Live data from Hacker News

MongoDB Performance & Durability (2010)

redbeard0531.s3.amazonaws.com

11–12 of 12 posts

Re: MongoDB Performance & Durability (2010)

#11
post #5
post #4

Earlier quoted context omitted.

As I would put it: In the event of a single server crash, Mongo may need to be restored from backup, or another master. CouchDB handles this much better, and can just restart where it left off. But in the worst possible single-server scenario, there's smoke coming out of your server and the hard drive is toast. CouchDB and MongoDB perform about the same - if you had replication or a recent backup, you are fine. If yo…

If you are running with journaling enabled, you should get a much stronger crash recovery case. In the event of a crash, the journal will be replayed: http://www.mongodb.org/display/DOCS/Journaling

And that is a good feature on a database to have! Why not make it the default?

Re: MongoDB Performance & Durability (2010)

#12
post #11
post #5

Earlier quoted context omitted.

If you are running with journaling enabled, you should get a much stronger crash recovery case. In the event of a crash, the journal will be replayed: http://www.mongodb.org/display/DOCS/Journaling

And that is a good feature on a database to have! Why not make it the default?

When we added it, being a new feature the decision was made not to initially flip it to default in case of bugs, unexpected behavior, etc.

As noted, it's possible that will change in future releases; there's been a lot of improvements to journaling since its initial release.

Post reply on HN