4 ms·
Relevant: Foursquare's post-mortem with mongodb. https://groups.google.com/forum/m/#!topic/mongodb-user/UoqU8ofp134 https://groups.google.com/forum/m/#!topic/mo
by leothekim 11y ago
Relevant: Foursquare's post-mortem with mongodb. https://groups.google.com/forum/m/#!topic/mongodb-user/UoqU8ofp134 https://groups.google.com/forum/m/#!topic/mongodb-user/UoqU8...
- technion 11y agoI'm hoping I'm reading this wrong. Because what I'm reading is "A database grew to 67GB on a server with only 66GB RAM". And apparently in that situation you can expect performance to tank until a service is unusable?
- mjevans 11y agoYou did not read that wrong. The performance tanked because the working set now required a disk hit. Each, and every, query, required a disk hit. That many IOs/sec, irrespective of the size could be enough.