[
https://issues.apache.org/jira/browse/CASSANDRA-3308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis updated CASSANDRA-3308:
--------------------------------------
Component/s: Core
Priority: Minor (was: Major)
Issue Type: Improvement (was: Bug)
> Add compaction_thread_priority back
> -----------------------------------
>
> Key: CASSANDRA-3308
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3308
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Affects Versions: 1.0.0
> Reporter: Brandon Williams
> Assignee: Jonathan Ellis
> Priority: Minor
> Labels: compaction
> Fix For: 1.0.0
>
> Attachments: 3308.txt
>
>
> In CASSANDRA-3104, this was removed with the following reasoning:
> bq. compaction_throughput_mb_per_sec is a more effective throttle on
> compaction.
> This turns out to be false in the majority of deployments. In many (if not
> most) situations, compaction is actually CPU bound, not IO bound, so
> multithreaded compaction is generally helpful, but the priority needs to be
> lowered in order to prevent it from stealing CPU used for reads/writes.
> Compaction is always CPU bound on both real hardware (sw raid0 with two SATA
> disks) and on a rackspace cloud server (though my understanding is they are
> back by a raid10 array underneath) however I suspect even a single drive is
> fast enough to handle the ~20MB/s that compaction is currently performing
> when unthrottled.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
