s that we will
have about 50GB of uncompressed data per day)
On Sat, Sep 18, 2010 at 3:46 AM, Benjamin Black wrote:
> It appears you are doing several things that assure terrible
> performance, so I am not surprised you are getting it.
>
Ok, let's see... explanations go below.
&
Hello,
On Wed, Sep 15, 2010 at 3:53 AM, Jonathan Ellis 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 Cassa
Hello,
On Wed, Sep 15, 2010 at 3:45 AM, Chen Xinli wrote:
[cut]
>>
> Disable row cache is ok, but key cache should be enabled. It use little
> memory, but reading peformance will improve a lot.
Hmm, I've tested with key cache enabled (100%) and I am pretty sure
that this really doesn't help si
Hey,
we are considering using Cassandra for quite large project and because
of that I made some tests with Cassandra. I was testing performance
and stability mainly.
My main tool was stress.py for benchmarks (or equivalent written in
C++ to deal with python2.5 lack of multiprocessing). I will foc
