[
https://issues.apache.org/jira/browse/CASSANDRA-5348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13606153#comment-13606153
]
Sylvain Lebresne commented on CASSANDRA-5348:
---------------------------------------------
For the record, I'm not convinced this is a good idea.
I wholeheartedly agree that we need something better and that the row cache is
not to be used in every workload.
But in the meantime, there is workloads in which the row cache works well. My
experience with a relatively standard use of Cassandra was that about 1/3 of
the column families were simple static column families. For those, the row
cache is useful and does more good than harm. That's not nothing.
And more importantly, I don't understand the rush in removing it. Chances are,
we'll have a better solution by 2.1 (and I'm all for making that a priority of
2.1). What should these people that use the row cache correctly do? They'll
have to setup a memcache or some other external solution just for 2.0? Seems
like we penalizing people that use a tool correctly because some other doesn't
(and I'm not blaming new people for expecting the row cache to be a query
cache, but I do have a problem penalizing experienced people).
What if instead we continue to educate people just one more version on when to
not use the current row cache (let's blog about it, let's send a mail on the
user list, ...)?
Anyway, just wanted to voice my opinion.
> 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
