Wednesday, April 9, 2014
Why aren't multi-object updates atomic?
Losing ACID across shards isn't an excuse for not having it within a shard. Applications control the shard key and can co-locate data that would benefit from this feature. Performance imperfections in the product, limits in the product and application data models will require this in some deployments.
Subscribe to:
Post Comments (Atom)
Sysbench vs MySQL on a small server: no new regressions, many old ones
This has performance results for InnoDB from MySQL 5.6.51, 5.7.44, 8.0.X, 8.4.8 and 9.7.0 on a small server with sysbench microbenchmarks. T...
-
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...
-
This has results to measure the impact of calling fsync (or fdatasync) per-write for files opened with O_DIRECT. My goal is to document the ...
-
I previously used math to explain the number of levels that minimizes write amplification for an LSM tree with leveled compaction. My answe...
No comments:
Post a Comment