Take the 2-minute tour ×
Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.

I know that MongoDB will use available free memory for caching, and swap to disk as needed to yield memory to other applications on the same server. For the best performance you'll want to have enough RAM to keep your indices and frequently used data ("working set") in memory.

So let's assume that I have 1 GB of data in MySQL which took 5 GB of disk space when it restored in MongoDB. Currently I have 2 GB of RAM, when we run analytic queries, MongoDb took 6 times more than the excecution time in MySql.

As my "working Set" is around 500MB and 1GB free RAM on my Machine instead of that query performance is very poor than MySQL so that I am a bit confused about how to calculate how much RAM I need to run analytic queries in MongoDB so that query execution time could be better than MySql.

share|improve this question
it's not clear that the slow speed was related to insufficient RAM. Did you have optimal indexes on MongoDB queries? Were indexes and working set "warm" (aka already in RAM)? More information would be needed to answer this. –  Asya Kamsky Jul 4 '13 at 19:55
add comment

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.