I have reviewed the evolution and results of adapting TPC-C benchmarks to MongoDB. But in vldb2019's paper, only single replica-set benchmark is available.So I'm wonder that if any benchmark for the sharding cluster has been conducted? After all the 4.2 version has already released for a few months.
--
You received this message because you are subscribed to the Google Groups "mongodb-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mongodb-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-dev/14479921-aecc-49f2-9572-6fc57a89aa31%40googlegroups.com.
Hi Scooby,With paper having a deadline in February 2019 only replica set transactions were available. I’m in the process of updating the benchmarks for sharded TPC-C and I’m hoping to write-up results for next year’s conference. Unfortunately this I’ve got additional work I do (research and publication can take at most only 20% of my time) it’s been slow going, I’m currently comparing performance of 4.0 vs 4.2 replica set TPC-C before moving forward to full sharded measurements (which may require additional tweaks to the code).Thanks for your interest and let me know if you have any other questions.Asya Kamsky
On Sun, Oct 27, 2019 at 23:37 Scooby Doo <huanmi...@gmail.com> wrote:
I have reviewed the evolution and results of adapting TPC-C benchmarks to MongoDB. But in vldb2019's paper, only single replica-set benchmark is available.--So I'm wonder that if any benchmark for the sharding cluster has been conducted? After all the 4.2 version has already released for a few months.
You received this message because you are subscribed to the Google Groups "mongodb-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mongo...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-dev/14479921-aecc-49f2-9572-6fc57a89aa31%40googlegroups.com.