the thing that will help most in 0.5 is to increase your
KeysCachedFraction to 0.2 or even more, depending on your workload.
On Sat, Jan 30, 2010 at 5:23 AM, Suhail Doshi digitalwarf...@gmail.com wrote:
An issue I've been seeing is it's really hard to scale Cassandra with reads.
I've run top,
See http://hudson.zones.apache.org/hudson/job/Cassandra/339/changes
Changes:
[jbellis] imrove Streaming commenting. patch by jbellis
[jbellis] merge from 0.5
[eevans] make builds smarter
- do not needlesssly regenerate avro code on each run
- fix javac src path for thrift generated code
According jconsole on the main table I am having issues with:
Capacity: 1164790
HitRate: .54
Size: 99753
Right now my KeysCachedFraction is 0.2. The current memory allocated is 3G.
What's a suggested KeysCachedFraction value?
Suhail
On Sat, Jan 30, 2010 at 5:58 AM, Jonathan Ellis
you want to get hitrate to 0.9 or so, i.e. 90% of index lookups don't
have to hit disk. play with KCF and see what happens. and use
jconsole to see how close you are getting to your 3GB limit (hit the
GC button to see how much memory is really being used, and then add
25% or so for a reasonable
Haven't seen much success between 0.1, 0.2, 0.3
On Sat, Jan 30, 2010 at 4:04 PM, Jonathan Ellis jbel...@gmail.com wrote:
you want to get hitrate to 0.9 or so, i.e. 90% of index lookups don't
have to hit disk. play with KCF and see what happens. and use
jconsole to see how close you are
