From: Miao Xie <miaoxie@huawei.com>
To: Fengguang Wu <fengguang.wu@intel.com>, Tejun Heo <tj@kernel.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [BUG]Writeback Cgroup/Dirty Throttle: very small buffered write thoughput caused by writeback cgroup and dirty thottle
Date: Thu, 12 May 2016 09:11:33 +0800 [thread overview]
Message-ID: <5733D845.2030709@huawei.com> (raw)
In-Reply-To: <57333E75.3080309@huawei.com>
Cc linux-kernel mail list
on 2016/5/11 at 22:15, Miao Xie wrote:
> Hi, Tejun and Fengguang
>
> I found that buffered write thoughput was dropped down by writeback cgroup and dirty thottle on
> 4.6-rc7 kernel. If I ran benchmark on the top block cgroup, the thoughput was more than 1500MB/s.
> If I ran benchmark on a new block cgroup, the thoughput was down to 4MB/s.
>
> Steps to reproduce:
> # mount -t cgroup2 cgroup <cgrp_mnt>
> # echo "+io +memory" > <cgrp_mnt>/cgroup.subtree_control
> # mkdir <cgrp_mnt>/aaa
> # echo $$ > <cgrp_mnt>/aaa/cgroup.procs
> # fio test.config
> job0: (g=0): rw=write, bs=4K-4K/4K-4K/4K-4K, ioengine=psync, iodepth=1
> fio-2.2.8
> Starting 1 thread
> Jobs: 1 (f=1): [W(1)] [3.7% done] [0KB/4000KB/0KB /s] [0/1000/0 iops] [eta 04m:50s]
>
> Fio configuration is:
> [global]
> bs=4K
> direct=0
> ioengine=psync
> iodepth=1
> directory=/mnt/ext4/tstdir0
> time_based
> runtime=300
> group_reporting
> size=16G
> sync=0
> max_latency=120000000
> thread
>
> [job0]
> numjobs=1
> rw=write
>
> My box has 48 cores and 188GB memory, but I set
> vm.dirty_background_bytes = 268435456
> vm.dirty_bytes = 536870912
>
> if I set vm.dirty_background_bytes and vm.dirty_bytes to be a large number(vm.dirty_background_bytes = 3GB,
> vm.dirty_bytes = 4GB), then fio thoughput would be more than 1500MB/s. and then if I reset them to the original
> value(the above ones), the thoughout would be down to 500MB/s.
>
> And according my debug, I found fio sleeped for 1ms every time we dirty a page(balance dirty pages) when
> the thoughput was down to 4MB/s, it might be a bug of dirty throttle when we open write back cgroup, I think.
>
> Tejun and Fengguang, please let me know what you guys think about this issue, and if you have
> any suggestions for possible solutions, Any input is greatly appreciated!
>
> Thanks
> Miao
next parent reply other threads:[~2016-05-12 1:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <57333E75.3080309@huawei.com>
2016-05-12 1:11 ` Miao Xie [this message]
2016-05-12 15:32 ` [BUG]Writeback Cgroup/Dirty Throttle: very small buffered write thoughput caused by writeback cgroup and dirty thottle Tejun Heo
2016-05-13 6:11 ` Miao Xie
2016-05-27 18:24 ` Tejun Heo
2016-05-27 18:34 ` [PATCH block/for-4.7-fixes] writeback: use higher precision calculation in domain_dirty_limits() Tejun Heo
2016-05-30 8:05 ` Jan Kara
2016-05-30 14:55 ` Jens Axboe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5733D845.2030709@huawei.com \
--to=miaoxie@huawei.com \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.