[
https://issues.apache.org/jira/browse/CASSANDRA-5348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13614610#comment-13614610
]
Jonathan Ellis commented on CASSANDRA-5348:
-------------------------------------------
How about removing on-heap cache as a compromise?
> 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
