Take a look here:
Response Time (s)
Transaction % Average : 90th % Total Rollbacks %
------------ ----- --------------------- ----------- --------------- -----
Delivery 3.98 0.211 : 0.266 274829 0 0.00
New Order 44.78 0.157 : 0.187 3090951 30925 1.00
Order Status 3.99 0.149 : 0.179 275357 0 0.00
Payment 42.76 0.150 : 0.180 2951361 0 0.00
Stock Level 3.99 0.152 : 0.182 275564 92070 33.41
50606.82 new-order transactions per minute (NOTPM)
60.5 minute duration
0 total unknown errors
31 second(s) ramping up
If you know what this output is from, and you know what 50K TPM means… your probably curious about these #’s. I am probably tantalizing you right now in fact. But I am not going to tell you more, not yet. So go ahead and guess. Better yet come listen to me talk at the user conference…
50K is the highest number I can ever remember getting for DBT2.
*** now around 57k ***
Sure, when talking about a 1 node system.
When talking about MySQL Cluster, breaking 100K is so last year:
http://mikaelronstrom.blogspot.com/2008/09/linear-scalability-of-mysql-cluster.html
Sure throw extra systems into the mix… Its like comparing apples and bunnies … two different things.