Hello, On Wed, Sep 15, 2010 at 3:53 AM, Jonathan Ellis <jbel...@gmail.com> wrote: > The key is that while Cassandra may read less rows per second than > MySQL when you are i/o bound (as you are here) because of SSTable > merging (see http://wiki.apache.org/cassandra/MemtableSSTable), you > should be using your Cassandra rows as materialized views so that each > query is a single row lookup rather than many. >
Thanks for your reply Jonathan! Of course there is advantage that for certain purposes you could store a lot of columns for single row and performance is still almost the same as with single column. But to be honest I'm pretty disappointed that Cassandra doesn't really scale linearly (or "semi-linearly" :)) when adding new machines. I expected that 8-machines cluster will easily beat single MySQL when there is much more data than RAM. Cheers, Kamil
