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.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

On my database server right now I have 16GB of ram and an 8GB capped collection with about 4GB of indexes. So I may understand this wrong but shouldn't this only ever use around 12GB of my RAM or maybe a bit more? After about 2 weeks of running the database it starts to act like it no longer fits into memory with insert speeds slowing down significantly and I have to repair the database. Am I just misunderstanding the way this should work?

share|improve this question

Check out

You might be running into a similar issue. Do you have several indexes on your data? Can you do a db.coll.stats()? And maybe show some output of mongostat while it's running slower?

I've heard similar complaints in the past, but haven't actually used capped collections myself.

share|improve this answer
Oh good find I'll keep an eye on my indexes and get some stats posted if it happens again. – Hersha Apr 18 '12 at 18:43

Your Answer


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

Not the answer you're looking for? Browse other questions tagged or ask your own question.