On Thu, Aug 22, 2013 at 7:53 PM, Faraaz Sareshwala < fsareshw...@quantcast.com> wrote:
> According to the datastax documentation [1], there are two types of row > cache providers: > ... > The off-heap row cache provider does indeed invalidate rows. We're going > to look into using the ConcurrentLinkedHashCacheProvider. Time to read > some source code! :) > Thanks for the follow up... I'm used to thinking of the ConcurrentLinkedHashCacheProvider as "the row cache" and forgot that SerializingCacheProvider might have different invalidation behavior. Invalidating the whole row on write seems highly likely to reduce the overall performance of such a row cache. :) The criteria for use of row cache mentioned up-thread remain relevant. In most cases, you probably don't actually want to use the row cache. Especially if you're using ConcurrentLinkedHashCacheProvider and creating long lived, on heap objects. =Rob
