Hi, In 99% of use cases Cassandra's row cache is not something you should look into. Leveraging page cache yields good results and if accounted for can provide you with performance increase on read side. I'm not a fan of a default row cache implementation and its invalidation mechanism on updates so you really need to be careful when and how you use it. There isn't much to configuration as there is to your use case. Maybe explain what are you trying to solve with row cache and people can get into discussion with more context.
Regards, Matija On Sat, Mar 11, 2017 at 9:15 PM, preetika tyagi <preetikaty...@gmail.com> wrote: > Hi, > > I'm new to Cassandra and trying to get a better understanding on how the > row cache can be tuned to optimize the performance. > > I came across think this article: https://docs. > datastax.com/en/cassandra/3.0/cassandra/operations/ > opsConfiguringCaches.html > > And it suggests not to even touch row cache unless read workload is > 95% > and mostly rely on machine's default cache mechanism which comes with OS. > > The default row cache size is 0 in cassandra.yaml file so the row cache > won't be utilized at all. > > Therefore, I'm wondering how exactly I can decide to chose to tweak row > cache if needed. Are there any good pointers one can provide on this? > > Thanks, > Preetika >
