MongoDB 3.0 is almost here. It includes the WiredTiger storage engine which is very impressive. Alas, now we are told that the original storage engine has performance problems. I am shocked. Who knew? Not anyone reading their documentation. I don't understand why companies play this game. Be honest with your users as this goes a long way to building a solid and educated community. I hold MySQL to the same standard. Lets us not forget that awesome manual section on atomic operations.
Don't let the marketing team have editorial control over the documentation team.
Edit: an era has ended, the section on atomic operations has been removed from the MySQL manual.
Subscribe to:
Post Comments (Atom)
How efficient is RocksDB for IO-bound, point-query workloads?
How efficient is RocksDB for workloads that are IO-bound and read-only? One way to answer this is to measure the CPU overhead from RocksDB a...
-
I need stable performance from the servers I use for benchmarks. I also need servers that don't run too hot because too-hot servers caus...
-
I previously used math to explain the number of levels that minimizes write amplification for an LSM tree with leveled compaction. My answe...
-
This provides additional results for Postgres versions 11 through 16 vs Sysbench on a medium server. My previous post is here . The goal is ...
Mark, my group owns documentation at MongoDB. We strive for accuracy above all else. If there are particular pages that need improvement, please let us know. The Docs project is a public Jira project (https://jira.mongodb.org/browse/DOCS) and you have filed tickets in the past. When you do, we work hard to make corrections.
ReplyDeleteThanks. I have already filed a few requests and the response has been excellent.
Delete