[
https://issues.apache.org/jira/browse/CASSANDRA-2449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099731#comment-13099731
]
Brandon Williams commented on CASSANDRA-2449:
---------------------------------------------
+1
> Deprecate or modify per-cf memtable sizes in favor of the global threshold
> --------------------------------------------------------------------------
>
> Key: CASSANDRA-2449
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2449
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Stu Hood
> Assignee: Jonathan Ellis
> Fix For: 1.0
>
> Attachments: 2449.txt
>
>
> The new memtable_total_space_in_mb setting is an excellent way to cap memory
> usage for memtables, and one could argue that it should replace the per-cf
> memtable sizes entirely. On the other hand, people may still want a knob to
> tune to flush certain cfs less frequently.
> I think a best of both worlds approach might be to deprecate the
> memtable_(throughput|operations) settings, and replace them with a preference
> value, which controls the relative memory usage of one CF versus another (all
> CFs at 1 would mean equal preference). For backwards compatibility, we could
> continue to read from the _throughput value and treat it as the preference
> value, while logging a warning.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
