From: Michal Hocko <mhocko@kernel.org>
To: "Bruno Prémont" <bonbons@linux-vserver.org>
Cc: cgroups@vger.kernel.org, linux-mm@kvack.org,
Johannes Weiner <hannes@cmpxchg.org>,
Vladimir Davydov <vdavydov.dev@gmail.com>,
Chris Down <chris@chrisdown.name>
Subject: Re: Memory CG and 5.1 to 5.6 uprade slows backup
Date: Thu, 9 Apr 2020 12:34:00 +0200 [thread overview]
Message-ID: <20200409103400.GF18386@dhcp22.suse.cz> (raw)
In-Reply-To: <20200409121733.1a5ba17c@hemera.lan.sysophe.eu>
On Thu 09-04-20 12:17:33, Bruno Prémont wrote:
> On Thu, 9 Apr 2020 11:46:15 Michal Hocko <mhocko@kernel.org> wrote:
> > [Cc Chris]
> >
> > On Thu 09-04-20 11:25:05, Bruno Prémont wrote:
> > > Hi,
> > >
> > > Upgrading from 5.1 kernel to 5.6 kernel on a production system using
> > > cgroups (v2) and having backup process in a memory.high=2G cgroup
> > > sees backup being highly throttled (there are about 1.5T to be
> > > backuped).
> >
> > What does /proc/sys/vm/dirty_* say?
>
> /proc/sys/vm/dirty_background_bytes:0
> /proc/sys/vm/dirty_background_ratio:10
> /proc/sys/vm/dirty_bytes:0
> /proc/sys/vm/dirty_expire_centisecs:3000
> /proc/sys/vm/dirty_ratio:20
> /proc/sys/vm/dirty_writeback_centisecs:500
Sorry, but I forgot ask for the total amount of memory. But it seems
this is 64GB and 10% dirty ration might mean a lot of dirty memory.
Does the same happen if you reduce those knobs to something smaller than
2G? _bytes alternatives should be useful for that purpose.
[...]
> > Is it possible that the reclaim is not making progress on too many
> > dirty pages and that triggers the back off mechanism that has been
> > implemented recently in 5.4 (have a look at 0e4b01df8659 ("mm,
> > memcg: throttle allocators when failing reclaim over memory.high")
> > and e26733e0d0ec ("mm, memcg: throttle allocators based on
> > ancestral memory.high").
>
> Could be though in that case it's throttling the wrong task/cgroup
> as far as I can see (at least from cgroup's memory stats) or being
> blocked by state external to the cgroup.
> Will have a look at those patches so get a better idea at what they
> change.
Could you check where is the task of your interest throttled?
/proc/<pid>/stack should give you a clue.
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2020-04-09 10:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-09 9:25 Memory CG and 5.1 to 5.6 uprade slows backup Bruno Prémont
2020-04-09 9:46 ` Michal Hocko
2020-04-09 10:17 ` Bruno Prémont
2020-04-09 10:34 ` Michal Hocko [this message]
2020-04-09 15:09 ` Bruno Prémont
2020-04-09 15:24 ` Chris Down
2020-04-09 15:40 ` Bruno Prémont
2020-04-09 17:50 ` Chris Down
2020-04-09 17:56 ` Chris Down
2020-04-09 15:25 ` Michal Hocko
2020-04-10 7:15 ` Bruno Prémont
2020-04-10 8:43 ` Bruno Prémont
[not found] ` <20200410115010.1d9f6a3f@hemera.lan.sysophe.eu>
[not found] ` <20200414163134.GQ4629@dhcp22.suse.cz>
2020-04-15 10:17 ` Bruno Prémont
2020-04-15 10:24 ` Michal Hocko
2020-04-15 11:37 ` Bruno Prémont
2020-04-14 15:09 ` Bruno Prémont
2020-04-09 10:50 ` Chris Down
2020-04-09 11:58 ` Bruno Prémont
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=20200409103400.GF18386@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=bonbons@linux-vserver.org \
--cc=cgroups@vger.kernel.org \
--cc=chris@chrisdown.name \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.org \
--cc=vdavydov.dev@gmail.com \
/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).