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)
Fixing some of the InnoDB scan perf regressions in a MySQL fork
I recently learned of Advanced MySQL , a MySQL fork, and ran my sysbench benchmarks for it. It fixed some, but not all, of the regressions f...
-
This provides additional results for Postgres versions 11 through 16 vs Sysbench on a medium server. My previous post is here . The goal is ...
-
MySQL 8.0.35 includes a fix for bug 109595 and with that fix the QPS is almost 4X larger on the read+write benchmark steps compared to MyS...
-
I am trying out a dedicated server from Hetzner for my performance work. I am trying the ax162-s that has 48 cores (96 vCPU), 128G of RAM a...
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