undefined | Better HN

0 pointslelanthran5y ago0 comments

> The last benchmark panel, https://raw.githubusercontent.com/scottrogowski/mongita/mast..., shows cold starts where I test it without cache. So in that, it does hit the disk.

Okay, so looking at the first two tests - "Retrieve all documents" and "Get 1000 documents by ID" ...

If you switch the order around, does it make a difference to the benchmark? Because I suspect that the first test preloads all records into RAM, and the second test simply searches RAM, which is not what we usually do with SQLite. We don't cache all records before searching.

Switch those first two tests around, and lets see if it makes a difference.

0 comments

1 comments · 1 top-level

scottrogowski5y ago

You're right. Fixed. SQLite is more-so the winner but Mongita appears to squeak ahead in id lookups https://github.com/scottrogowski/mongita/blob/master/assets/... (to be fair, it might be the thin translation layer I built). Regular MongoDB struggles a lot and I don't think I'm being unfair to it in any way afaik.

Thank you for pointing that all out.

j / k navigate · click thread line to collapse