Hi
I was wondering if Cassandra has any plans for supporting atomic compare and
swap operation on a column value? Compare could be on timestamp for the column
or the column value itself and the write of course is on the column value + a
new timestamp. If there are no plans on supporting such an
usage
yes, it is expected that writes are cpu-bound.
On Fri, Jun 11, 2010 at 11:29 AM, Rishi Bhardwaj wrote:
> I think it would be a good exercise to know what the CPU bottleneck is on
> the write path. The fact that Cassandra optimizes disk I/O for writes would
> only go so far if the
gt;>you can cause them to stack up on top of the available CPU and memory
>>resources.
>
>>In such a case (continuous bulk writes), you are causing all of these
>>costs to be taken in more of a synchronous (not delayed) fashion. You
>>are not allowing the background proce
ot delayed) fashion. You
are not allowing the background processing that helps reduce client
blocking (by deferring some processing) to do its magic.
On Thu, Jun 10, 2010 at 7:42 PM, Rishi Bhardwaj wrote:
> Hi
> I am investigating Cassandra write performance and see very heavy CPU usage
>
Hi
I am investigating Cassandra write performance and see very heavy CPU usage
from Cassandra. I have a single node Cassandra instance running on a dual core
(2.66 Ghz Intel ) Ubuntu 9.10 server. The writes to Cassandra are being
generated from the same server using BatchMutate(). The client ma
