3 ms·
Postgres literally beats MongoDB at JSON in benchmarks. Y'know, the thing that's supposed to be Mongo's bread and butter?
by HideousKojima 5y ago
Postgres literally beats MongoDB at JSON in benchmarks. Y'know, the thing that's supposed to be Mongo's bread and butter?
- jd_mongodb 5y agoWhich benchmark is that?
- HideousKojima 5y agohttps://www.enterprisedb.com/news/new-benchmarks-show-postgres-dominating-mongodb-varied-workloads https://www.enterprisedb.com/news/new-benchmarks-show-postgr...
- ghartnett 5y agoUnfortunately that benchmark was very inaccurate. They tuned the postgres configuration and didn't tune MongoDB. They also used an unsupported, experimental driver without connection pooling on MongoDB. For example: they measured Query B execution time on postgres: 41m3s, mongodb: 1h13m3s. When MongoDB measured Query B with a supported driver, the execution time was only 3m30s more than 10x faster than postgres! You'll find details here: https://www.mongodb.com/blog/post/benchmarking-do-it-right-or-dont-do-it-at-all https://www.mongodb.com/blog/post/benchmarking-do-it-right-o...
- gqewogpdqa 5y agoThanks for that info. Statistics, misunderstandings, lies, benchmarks, database benchmarks...
- toqy 5y agoMongodb was a lot easier to manipulate json in for a while vs postgres, but once postgres got json path support it evened out a bit imo. Say you have some json and nested in it somewhere is an array of objects, and you want to just map over that and update those objects. I was writing a migration to do that in Postgres <11 once and it was not fun to try and figure out how to do it. I haven't worked with Mongo in years though, so no clue how it has evolved since like 2015.