Got it. Thanks again, Aaron.
-- Y.
On Tue, Dec 4, 2012 at 3:07 PM, aaron morton wrote:
> Does this mean we should not enable row caches until we are absolutely
> sure about what's hot (I think there is a reason why row caches are
> disabled by default) ?
>
> Yes and Yes.
> Row cache takes mem
> Does this mean we should not enable row caches until we are absolutely sure
> about what's hot (I think there is a reason why row caches are disabled by
> default) ?
Yes and Yes.
Row cache takes memory and CPU, unless you know you are getting a benefit from
it leave it off. The key cache and
Hi Aaron,
Thank you,and your explanation makes sense. At the time, I thought having
1GB of row cache on each node was plenty enough, because there was an
aggregated 6GB cache, but you are right, with each row in 10's of MBs, some
of the nodes can go into a constant load and evict cycle and would
> Row Cache: size 1072651974 (bytes), capacity 1073741824 (bytes), 0
> hits, 2576 requests, NaN recent hit rate, 0 save period in seconds
So the cache is pretty much full, there is only 1 MB free.
There were 2,576 read requests that tried to get a row from the cache. Zero of
those had
Does anyone have any comments/suggestions for me regarding this? Thanks
I am trying to understand some strange behavior of cassandra row cache. We
> have a 6-node Cassandra cluster in a single data center on 2 racks, and the
> neighboring nodes on the ring are from alternative racks. Each node
