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)
CPU-bound Insert Benchmark vs Postgres on 24-core and 32-core servers
This has results for Postgres versions 12 through 18 with a CPU-bound Insert Benchmark on 24-core and 32-core servers. A report for MySQL ...
-
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