I would think that compaction_throughput_kb_per_sec does have indirect impact
on disk IO. High number means or setting it to 0 means there is no
throttling on how much IO is being performed. Wouldn't it impact normal
reads from disk during the time when disk IO or util is high which
I am using the default 16MB when running repair. but the disk io is still
quite high:
Device: rrqm/s wrqm/s r/s w/srkB/swkB/s avgrq-sz
avgqu-sz await r_await w_await svctm %util
sdb 136.00 0.00 506.00 26.00 63430.00 5880.00 260.56
101.73 224.38
compaction throughput doesn't affect flushing or reads
On Mon, Sep 26, 2011 at 7:40 AM, Yan Chunlu springri...@gmail.com wrote:
I am using the default 16MB when running repair. but the disk io is still
quite high:
Device: rrqm/s wrqm/s r/s w/s rkB/s wkB/s avgrq-sz
I would think that compaction_throughput_kb_per_sec does have indirect impact
on disk IO. High number means or setting it to 0 means there is no
throttling on how much IO is being performed. Wouldn't it impact normal
reads from disk during the time when disk IO or util is high which
compaction is
okay, thanks!
On Mon, Sep 26, 2011 at 10:38 PM, Jonathan Ellis jbel...@gmail.com wrote:
compaction throughput doesn't affect flushing or reads
On Mon, Sep 26, 2011 at 7:40 AM, Yan Chunlu springri...@gmail.com wrote:
I am using the default 16MB when running repair. but the disk io is still
