[
https://issues.apache.org/jira/browse/CASSANDRA-688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12800282#action_12800282
]
Ryan King commented on CASSANDRA-688:
-------------------------------------
I've only looked through the patches briefly, and being able to set the
capacity by rows is certainly an improvement, but it would be nice if it
weren't per-SSTable, but per CF. I know that the cache-per-CF thing didn't work
well, so maybe this isn't possible.
> cache refinements
> -----------------
>
> Key: CASSANDRA-688
> URL: https://issues.apache.org/jira/browse/CASSANDRA-688
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Jonathan Ellis
> Assignee: Jonathan Ellis
> Priority: Minor
> Fix For: 0.9
>
> Attachments: 0001-move-cache-classes-to-cassandra.cache-package.txt,
> 0002-extract-InstrumentingCache-from-jmx-code.txt,
> 0003-add-JMXAggregatingCache-to-present-all-the-SSTR-keycac.txt,
> 0004-change-RowsCachedFraction-option-to-RowsCached-specifi.txt,
> 0005-allow-setting-row-cache-size-from-jmx.txt,
> 0006-approximate-capacity-setting-in-key-cache-by-adjusting.txt
>
>
> (continued from CASSANDRA-678)
> - instrument keycache in a way that doesn't make performance suck
> - add Ryan's suggestion of absolute row count config option
> - adjust cache size live
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
