3 ms·
Ok, fair enough. Then the answer is yes, they did fix it. :) I guess I'll give it another look then. But I'm still a little wary of a database built by peopl
by jedberg 12y ago
Ok, fair enough. Then the answer is yes, they did fix it. :)
I guess I'll give it another look then.
But I'm still a little wary of a database built by people who ever thought that such behavior was acceptable for a database...
- nemo44x 12y agoI'd make sure you use the new storage engine, wiredtiger too if you give them another shot. The standard one works well on read heavy use cases but saturates I/O pretty quickly if you're doing a lot of updates that make documents grow if you don't take some precautions. I also agree, having a setting of "fire and forget", although useful in some (limited!) use cases, is not a sane default.