From: Chris Down <chris@chrisdown.name>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
Cc: Michal Hocko <mhocko@kernel.org>,
cgroups@vger.kernel.org,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Johannes Weiner <hannes@cmpxchg.org>,
"n.fahldieck@profihost.ag" <n.fahldieck@profihost.ag>,
Daniel Aberger - Profihost AG <d.aberger@profihost.ag>,
p.kramme@profihost.ag
Subject: Re: No memory reclaim while reaching MemoryHigh
Date: Sun, 28 Jul 2019 22:39:10 +0100 [thread overview]
Message-ID: <20190728213910.GA138427@chrisdown.name> (raw)
In-Reply-To: <9eb7d70a-40b1-b452-a0cf-24418fa6254c@profihost.ag>
Hi Stefan,
Stefan Priebe - Profihost AG writes:
>anon 8113229824
You mention this problem happens if you set memory.high to 6.5G, however in
steady state your application is 8G. What makes you think it (both its RSS and
other shared resources like the page cache and other shared resources) can
compress to 6.5G without memory thrashing?
I expect you're just setting memory.high so low that we end up having to
constantly thrash the disk due to reclaim, from the evidence you presented.
next prev parent reply other threads:[~2019-07-28 21:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-25 13:17 Stefan Priebe - Profihost AG
2019-07-25 14:01 ` Michal Hocko
2019-07-25 21:37 ` Stefan Priebe - Profihost AG
2019-07-26 7:45 ` Michal Hocko
2019-07-26 18:30 ` Stefan Priebe - Profihost AG
2019-07-28 21:11 ` Stefan Priebe - Profihost AG
2019-07-28 21:39 ` Chris Down [this message]
2019-07-29 5:34 ` Stefan Priebe - Profihost AG
2019-07-29 7:07 ` Stefan Priebe - Profihost AG
2019-07-29 7:45 ` Stefan Priebe - Profihost AG
2019-07-31 13:03 ` Michal Hocko
2019-07-25 14:53 ` Chris Down
2019-07-25 21:42 ` Stefan Priebe - Profihost AG
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=20190728213910.GA138427@chrisdown.name \
--to=chris@chrisdown.name \
--cc=cgroups@vger.kernel.org \
--cc=d.aberger@profihost.ag \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=n.fahldieck@profihost.ag \
--cc=p.kramme@profihost.ag \
--cc=s.priebe@profihost.ag \
/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