[
https://issues.apache.org/jira/browse/CASSANDRA-3143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13101509#comment-13101509
]
Pavel Yaskevich commented on CASSANDRA-3143:
--------------------------------------------
Comment from Jonathan:
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.
Hmm. I guess we could have the cache provider include a sizeInMemory method?
For serialized off-heap cache we can just use the FreeableMemory size(). For
on-heap cache we can use the serializedSize * liveRatio from the CF's memtable.
> Global caches (key/row)
> -----------------------
>
> Key: CASSANDRA-3143
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3143
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Pavel Yaskevich
> Assignee: Pavel Yaskevich
> Priority: Minor
> Labels: Core
> Fix For: 1.1
>
>
> Caches are 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
