MongoDB isn’t a write-to-disk application unlike SQL. So it writes
to a fsync queue first which actually gets managed by the OS (this
is fundamentally NoSQL here to not write straight to disk,
“Eventually Consistent”), since MongoDB does no memory management of
Added ontop of this is that you must load a part of the _id btree
each time you insert as well which is ever growing due to
insertions. This means that actually if you do mass inserts in a
short period of time you could end up loading more of the btree than
you need to because the older section of the btree have not been
seen as stale yet.
How many “strange” explanations have you counted in the above answer?
This blog is called myNoSQL and it is written by me, Alex Popescu, a software architect with a passion for open source and communities.
It records my readings, learnings, and opinions on NoSQL databases, polyglot persistence, and distributed systems -- subjects that I'm passionate about.
The opinions expressed here are my own, and no other party necessarily agrees with them.
If you feel I'm biased, I probably am.