On 10.09.2013, at 19:37, Robert Coli wrote:
> "Cassandra does not prevent a given node from writing to RAM faster than it
> can flush to disk"?
Yes, that is what I meant.
What remains unclear to me is what the oprational strategy is towards handling
an increase in writes or peaks.
Seems to
On Tue, Sep 10, 2013 at 2:30 AM, Jan Algermissen wrote:
> So in a sense, C* is designed to maximize IO write efficiency by
> pre-organizing write queries in memory. The more memory, the better the
> organization works (caveat GC).
>
http://en.wikipedia.org/wiki/Log-structured_merge-tree
"
The LS
Based on my tuning work with C* over the last days, I guess I reached the
following insights.
Maybe someone can confirm whether they make sense:
The more heap I give to Cassandra (up to the GC tipping point of ~8GB) the more
writes it can accumulate in memtables before doing IO.
The more write
