[
https://issues.apache.org/jira/browse/CASSANDRA-14902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17151696#comment-17151696
]
Jeremy Hanna commented on CASSANDRA-14902:
------------------------------------------
I assumed that updating to 64 would be uncontroversial because that's what I
know many change it to (including myself) as a first step/starting point. If
we want to do more extensive comparison testing of different values, that's
fine, but I think it would depend on the goal. IO is going to be different for
every system and every workload/pattern is going to be somewhat unique. I
thought 64 would at least make it not *required* to change it from the default
as a first step.
> Update the default for compaction_throughput_mb_per_sec
> -------------------------------------------------------
>
> Key: CASSANDRA-14902
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14902
> Project: Cassandra
> Issue Type: Task
> Components: Local/Compaction, Local/Config
> Reporter: Jeremy Hanna
> Assignee: Jeremy Hanna
> Priority: Low
>
> compaction_throughput_mb_per_sec has been at 16 since probably 0.6 or 0.7
> back when a lot of people had to deploy on spinning disks. It seems like it
> would make sense to update the default to something more reasonable -
> assuming a reasonably decent SSD and competing IO. One idea that could be
> bikeshedded to death could be to just default it to 64 - simply to avoid
> people from having to always change that any time they download a new version
> as well as avoid problems with new users thinking that the defaults are sane.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
