cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Schuller <>
Subject Re: 0.7 memory usage problem
Date Mon, 27 Sep 2010 20:13:39 GMT
> You are saying I am doing 36000 inserts per second, when I am inserting 600
> rows, I thought that every row goes into one Node, so the work is done for a
> row not a column, so my assumption is NOT true, the work is done on a column
> level? so if I reduce the number of columns I will get a "substantial"
> improvement in performance?

I am not sure about actual numbers, but in general, there is a cost on
a per-column basis. I'm pretty sure it's lower than the per-row cost,
but it is still not free and should be on the same order of magnitude
as rows (I haven't benchmarked with this in mind; someone correct me
if I'm wrong). I.e., you can't expect to put an arbitrary amount of
columns into a batch mutation, even if it affects just one row, and
not have it affect performance. Consider that individual columns are
subject to conflict resolution, consistency guarantees and to indexed

Regarding reduction of column: You will definitely get a substantial
performance improvement in terms of "row mutations per second" by
decreasing the number of columns mutated in each row; however that is
comparing apples and oranges since you would be inserting less data.

> Also, what do you mean by "distributing the client load across the
> cluster",  I am doing the writing on Node1, the reading on Node2, and the
> maintenance on Node3 (disabled the maintenance for now).
> Do you think its better if I do writes on all 3 Nodes and reads on all 3
> Nodes as well?

The typical approach to real production use is to distribute requests
to all nodes in some kind of pseudo-random/round robin fashion. Smart
clients might keep track of up/down status of nodes and possibly even
to weighting based on performance characteristics of each node. But
the general idea is - spread the load out across all nodes.

Note however that depending on actual situation it need not matter
much. For example if you are no where near CPU bound nor network bound
on the Cassandra side, evening out the load of the RPC traffic does
not make much of a difference. But as a general recommendation,
distributing the load across machines is a good default choice of

(Of course not doing so should not cause the stack overflow you're
seeing, so this is a separate issue.)

/ Peter Schuller

View raw message