linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Chris Mason <clm@fb.com>, Dexuan Cui <decui@microsoft.com>,
	Theodore Ts'o <tytso@mit.edu>,
	Andreas Dilger <adilger.kernel@dilger.ca>,
	"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: ext4: performance regression introduced by the cgroup writeback support
Date: Wed, 23 Sep 2015 14:53:37 -0400	[thread overview]
Message-ID: <20150923185337.GK26647@mtj.duckdns.org> (raw)
In-Reply-To: <20150923161359.GB25218@ret.masoncoding.com>

On Wed, Sep 23, 2015 at 12:13:59PM -0400, Chris Mason wrote:
> > The issue is: under high CPU and disk I/O pressure, *some* processes can suffer from a very slow write speed (e.g., <1MB/s or even only 20KB/s), while the normal write speed should be at least dozens of MB/s.

So, I think I know what caused this regression.  Separate wb domains
shouldn't have been enabled on traditional hierarchies.  It doesn't
work there and leads to multiple wb domains competing on the same
blkcg and the bw estimation would go completely haywire.  Will update
soon.

Thanks.

-- 
tejun

  reply	other threads:[~2015-09-23 18:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-23 13:49 ext4: performance regression introduced by the cgroup writeback support Dexuan Cui
2015-09-23 16:13 ` Chris Mason
2015-09-23 18:53   ` Tejun Heo [this message]
2015-09-24  0:15     ` Dexuan Cui
2015-09-24  7:26     ` Dexuan Cui
2015-09-24  0:12   ` Dexuan Cui

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=20150923185337.GK26647@mtj.duckdns.org \
    --to=tj@kernel.org \
    --cc=adilger.kernel@dilger.ca \
    --cc=clm@fb.com \
    --cc=decui@microsoft.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).