On Wed, Apr 4, 2012 at 8:04 AM, aaron morton wrote:
> It depends on the workload.
>
> Increase the cache size until you see the hit rate decrease, or see it
> create memory pressure. Watch the logs for messages that the caches have
> been decreased.
>
> Take a look at the Recent Read Latency for t
It depends on the workload.
Increase the cache size until you see the hit rate decrease, or see it create
memory pressure. Watch the logs for messages that the caches have been
decreased.
Take a look at the Recent Read Latency for the CF. This is how long it takes to
actually read data on th
On Tue, Apr 3, 2012 at 11:49 AM, aaron morton wrote:
> Take a look at the key cache hit rate in nodetool cfstats.
>
> One approach is to increase the cache size until you do not see a matching
> increase in the hit rate.
>
Thanks Aaron, what do you think will be the ideal cache hit ratio where w
Take a look at the key cache hit rate in nodetool cfstats.
One approach is to increase the cache size until you do not see a matching
increase in the hit rate.
> Is there a limit to key cache size? I know that is all taken from heap but
> how much max we can go with setting the key cache size
Hi guys,
We are calculating key cache size right now. There is this column family
with ~ 100 million columns and right now we have the cache size set at 2
million.
I suspect that the active data we got is not all fitting in the 2 million
cache size and we at times are getting query execution time
