[
https://issues.apache.org/jira/browse/CASSANDRA-3049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13086407#comment-13086407
]
Jonathan Ellis commented on CASSANDRA-3049:
-------------------------------------------
Also: we should size the global cache in bytes. There are two possibly
approaches:
- Do it "manually" by estimating bytes from Key length plus CLHM overhead
- Use JAMM as we do for memtables
Since the key cache is simpler than a memtable, the first approach might be
workable here. But we know JAMM works reasonably well, so that's fine too.
> Global key cache
> ----------------
>
> Key: CASSANDRA-3049
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3049
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Jonathan Ellis
> Assignee: Pavel Yaskevich
> Priority: Minor
> Fix For: 1.0
>
>
> Key-cache-per-columnfamily is difficult to configure well as columnfamilies
> are added, similar to how memtables were difficult pre-CASSANDRA-2006.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
