But, companies like Twitter and Netflix certainly have the budget for Exadata (which is what clustrix wants to be when it grows up); they are using Cassandra instead not just because it scales on commodity hardware (the other price factor besides licensing) but also because it works across multiple datacenters which two-phase commit systems can't do no matter how big your budget is, and because its availability (failure tolerance) model is much more robust.
(Many NoSQL systems don't provide these advantages either, which is why lumping all non-relational systems together is usually not helpful.)
http://gigaom.com/cloud/clustrix-lifts-the-curtain-on-early-...
And plenty of folks use MySQL (and PogreSQL to a much lesser extent). You just can't scale those.
Edit: twitter cassandra link (don't know if this is the latest): http://engineering.twitter.com/2010/07/cassandra-at-twitter-...
So I guess that statement should be written as "you can't scale with just those". :)
Your benchmark is pretty much irrelevant because Clustrix sells hardware appliances, not the software standalone.
Edit: That's not to say MongoDB didn't fail your benchmark. But the issues you highlight (single mutex) are known. Test against a real database and your results don't look that impressive for a 10 node setup.
All that said, Clustrix looks great. Just make it available sans-hardware.