cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Brown (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-5348) Remove row cache until we can replace it with something better
Date Wed, 27 Mar 2013 01:25:15 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-5348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13614782#comment-13614782
] 

Jason Brown commented on CASSANDRA-5348:
----------------------------------------

Still looking for some blood, huh :) ? I think that is a reasonable compromise, as we resolve
some technical debt yet retain the better part of that implementation (the off heap part).

So, +1 to [~jbellis]'s suggestion.
                
> Remove row cache until we can replace it with something better
> --------------------------------------------------------------
>
>                 Key: CASSANDRA-5348
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5348
>             Project: Cassandra
>          Issue Type: Task
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: Vijay
>             Fix For: 2.0
>
>
> The row (partition) cache easily does more harm than good.  People expect it to act like
a query cache but it is very different than that, especially for the wide partitions that
are so common in Cassandra data models.
> Making it off-heap by default only helped a little; we still have to deserialize the
partition to the heap to query it.
> Ultimately we can add a better cache based on the ideas in CASSANDRA-1956 or CASSANDRA-2864,
but even if we don't get to that until 2.1, removing the old row cache for 2.0 is a good idea.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message