trafficserver-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yongming Zhao <>
Subject Re: persistent disk write at rate of ~4 MB/s
Date Sun, 19 Oct 2014 15:09:37 GMT
I don’t how bcache works with  the dir index sync writing, but I think those writes should
not be read until next server restart, hopes bcache is smart enough to pass those write through.

if you want, you may try the interim caching, which works inside of ATS.


> 在 2014年10月19日,下午11:01,Leif Hedstrom <> 写道:
> That sounds like the dir sync task. You can try changing the config to sync less frequently
and see if that affects it? On very large disks it probably has to get very long, basically
the dir sync throttles itself to not put too much pressure on the disks. Maybe we should make
that configurable too.
> -- Leif 
>> On Oct 19, 2014, at 2:55 AM, Timur Irmatov <> wrote:
>> Hi,
>> I see that my trafficserver writes to disk at a rate of around 4 MB/s
>> irregardless of client load (which is small, less than 50 Mbit/s, with
>> as low as 2 Mbit/s at nights). I observe it with iostat and Collectd/
>> Graphite, 24 hours. Why is it doing so?
>> I am using bcache with one SSD and four 1 TB SATA drives behind it. I
>> am concerned that this persistent write stream will lead to premature
>> wear of SSD cache. Can I do something about it?
>> I think my question should be in FAQ. I noticed this behaviour a
>> couple of years ago but never got to asking about it until now.
>> -- 
>> Timur Irmatov

- Yongming Zhao 赵永明

View raw message