@chris. Thanks. I wil keep you update if I find something @Joe. I am not telling this is a bad number. I am just telling this is still not enough for us ( in order to limit the number of nodes) ;o) If I look at the last bench, version 0.6.2 is around 13000w/s I should/would be able to reach 10000w/sec (in fact this is almost the case in non virtualized env.). I am just trying to understand where is the bottleneck.
What do you mean by "N+1 scaling"? Not sure to understand the expression. Thanks. On Saturday, June 19, 2010, Chris Dean wrote: >> @Chris, Did you get any bench you could share with us? > > We're still working on it. It's a lower priority task so it will take a > while to finish. So far we've run on all the AWS data centers in the US > and used several different setups. We also did a test on Rackspace with > one setup and some whitebox servers we had in the office. (The whitebox > servers are still running I believe.) > > I don't have the numbers here, but the fastest by far is the > non-virtualized whitebox servers. No real surprise. Rackspace was > faster than AWS US-West; US-West faster than the than US-East. > > We always use 3 Cassandra servers and one or two machines to run > stress.py. I don't think we're seeing the 7500 writes/sec so maybe our > config is wrong. You'll have to be patient until my colleague writes > this all up. > > Cheers, > Chris Dean > -- ............................................................ Olivier Mallassi OCTO Technology ............................................................ 50, Avenue des Champs-Elysées 75008 Paris Mobile: (33) 6 28 70 26 61 Tél: (33) 1 58 56 10 00 Fax: (33) 1 58 56 10 01 http://www.octo.com Octo Talks! http://blog.octo.com
