Our experience is that you want to have all your very hot data fit in the row cache (assuming you don’t have very large rows), and leave the rest for the OS. Unfortunately, it completely depends on your access patterns and data what is the right size for the cache - zero makes sense for a lot of cases.
Try out different sizes, and watch for row cache hit ratio and read latency. Ditto for heap sizes, btw - if your nodes are short on RAM, you may get better performance by running at lower heap sizes because OS caches will get more memory and your gc pauses will be shorter (though more numerous). /Janne On 23 Jan 2014, at 09:13 , Katriel Traum <katr...@google.com> wrote: > Hello list, > > I was if anyone has any pointers or some advise regarding using row cache vs > leaving it up to the OS buffer cache. > > I run cassandra 1.1 and 1.2 with JNA, so off-heap row cache is an option. > > Any input appreciated. > Katriel
