I have the same problem! 2013/3/11 Alain RODRIGUEZ <arodr...@gmail.com>
> I can add that I have JNA corectly loaded, from the logs: "JNA mlockall > successful" > > > 2013/3/11 Alain RODRIGUEZ <arodr...@gmail.com> > >> 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 <arodr...@gmail.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.png >>> >>> It 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 ? >>> >> >> > -- Atenciosamente, Sávio S. Teles de Oliveira voice: +55 62 9136 6996 http://br.linkedin.com/in/savioteles Mestrando em Ciências da Computação - UFG Arquiteto de Software Laboratory for Ubiquitous and Pervasive Applications (LUPA) - UFG
