What version are you using?Sounds like you have configured it correctly. Did you restart the node after changing the row_cache_size_in_mb ?The changes in GC activity are not huge and may not be due to cache activity. Have they continued after you enabled the row cache?What is the output from nodetool info?CheersOn 11/03/2013, at 5:30 AM, Sávio Teles <firstname.lastname@example.org> wrote:I have the same problem!
2013/3/11 Alain RODRIGUEZ <email@example.com>I can add that I have JNA corectly loaded, from the logs: "JNA mlockall successful"2013/3/11 Alain RODRIGUEZ <firstname.lastname@example.org>
Any clue on this ?Row cache well configured could avoid us a lot of disk read, and IO is definitely our bottleneck... If someone could explain why the row cache has so much impact on my JVM and how to avoid it, it would be appreciated :).2013/3/8 Alain RODRIGUEZ <email@example.com>
Hi,We have some issue having a high read throughput. I wanted to alleviate things by turning the row cache ON.I set the row cache to 200 on one node and enable caching 'ALL' on the 3 most read CF. There is the effect this operation had on my JVM: http://img692.imageshack.us/img692/4171/datastaxopscenterr.pngIt looks like the row cache was somehow stored in-heap. I looked at my cassandra.yaml and I have the following configuration: row_cache_provider: SerializingCacheProvider (which should be enough to store row cache off-heap as described above in this file: "SerializingCacheProvider serialises the contents of the row and stores it in native memory, i.e., off the JVM Heap")What's wrong ?
Sávio S. Teles de Oliveira