Insert benchmark: in-memory, high-concurrency, fast server - part 2

10 news today, 461 news this week, 3285 news in total. 166 Projects.
This is similar to the previous insert benchmark result for in-memory and high-concurrency except it uses 1 table rather than 16 to determine how a storage engine behaves with more contention. The results for 16 vs 1 table are more interesting on the IO-bound test where there are more stalls in the 1-table results.One example of performance lost from contention is the per-index mutex for InnoDB which is locked during pessimistic changes to the B-Tree. I know this has been improved over the years but the problem has not been eliminated.ConfigurationStart by reading my previous post. The test st...
Mysql
Date