4 ms·
While you're correct, I don't believe the point was that you had no control over it. The point was that their benchmarks came from using delayed-write setting a
by woogley 16y ago
While you're correct, I don't believe the point was that you had no control over it. The point was that their benchmarks came from using delayed-write setting and compared it against databases that ARE writing to disk. He's saying that mongo is cheating the benchmark by doing work after the timer has stopped.
- binspace 16y agoMaybe cheating is ok. Sure, there is a reason why it's faster. Maybe the guarantee of the write to disk is not as necessary as some people would believe. It's certainly not the same as writing to /dev/null. Maybe the developer can have other ways of guaranteeing consistency.