4 ms·
... but that usually doesn't mean you have to have your full data set in memory, only the hot parts. And even if so, one or two ~10 ms seeks during a query aren
by Nitramp 12y ago
... but that usually doesn't mean you have to have your full data set in memory, only the hot parts. And even if so, one or two ~10 ms seeks during a query aren't that terrible.
- brey 12y agomongodb recommends that your working set lives in memory, not your entire database - it's generally much cheaper to add more RAM than code in any case. a few seeks aren't terrible for small/medium applications, but when you're asking for thousands of queries a second any disk access is bad news.