I think you mean "900 million transactions per minute". Of course that overstates things since each TPC-C transaction entails a lot more than one write. TPC-C is about 2/3 read and 1/3 write, and each TPC transaction might do 20 low-level read+write operations (I'm actually not sure, but I think that's in the ballpark.)
In the NoSQL world many people have converged on a workload of 90% reads/10% writes to individual keys. We show 90/10 results on our performance page [1] but in this test we do 100% writes to stress the "transaction engine", which processes writes.
Since we have our SQL Layer [2] as well, we will run some more-comparable SQL tests in the future.
Comments
I think you mean "900 million transactions per minute". Of course that overstates things since each TPC-C transaction entails a lot more than one write. TPC-C is about 2/3 read and 1/3 write, and each TPC transaction might do 20 low-level read+write operations (I'm actually not sure, but I think that's in the ballpark.)
In the NoSQL world many people have converged on a workload of 90% reads/10% writes to individual keys. We show 90/10 results on our performance page [1] but in this test we do 100% writes to stress the "transaction engine", which processes writes.
Since we have our SQL Layer [2] as well, we will run some more-comparable SQL tests in the future.
[1] https://foundationdb.com/key-value-store/performance
[2] https://foundationdb.com/layers/sql
(Ah, yes, thank you, 900 million per minute. I typo'd.)
Nice performance page. It pre-answers my follow up question, which was how linear is scaling with more cores? Looks solid.