[
https://issues.apache.org/jira/browse/CASSANDRA-1007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12906349#action_12906349
]
Matthew F. Dennis commented on CASSANDRA-1007:
----------------------------------------------
does it make sense to still have a global default which is used when the flush
thresholds are not specified in the CF (i.e. *optionally* set them per CF)?
> Make memtable flush thresholds per-CF instead of global
> -------------------------------------------------------
>
> Key: CASSANDRA-1007
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1007
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Jonathan Ellis
> Assignee: Jon Hermes
> Priority: Minor
> Fix For: 0.7 beta 2
>
>
> This is particularly useful in the scenario where you have a few CFs with a
> high volume of overwrite operations; increasing the memtable size/op count
> means that you can do the overwrite in memory before it ever hits disk. Once
> on disk compaction is much more work for the system.
> But, you don't want to give _all_ your CFs that high of a threshold because
> the memory is better used elsewhere, and because it makes commitlog replay
> unnecessarily painful.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
