linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: Chris Down <chris@chrisdown.name>
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: Mon, 29 Jul 2019 07:34:13 +0200	[thread overview]
Message-ID: <2444c2d9-4c56-557a-5a25-c8ca25f94423@profihost.ag> (raw)
In-Reply-To: <20190728213910.GA138427@chrisdown.name>

Hi Chris,
Am 28.07.19 um 23:39 schrieb Chris Down:
> 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.
This is a current memory.stat now i would test with memory.high set to
7.9 or 8G.

Last week it was at 6.5G

 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?
If i issue echo 3 > drop_caches the usage always drops down to 5.8G


> 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.

This sounds interesting? How can i verify this? And what do you mean by
trashing the disk? swap is completely disabled.

I thought all memory which i can drop with drop_caches can be reclaimed?

Greets,
Stefan


  reply	other threads:[~2019-07-29  5:34 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
2019-07-29  5:34             ` Stefan Priebe - Profihost AG [this message]
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=2444c2d9-4c56-557a-5a25-c8ca25f94423@profihost.ag \
    --to=s.priebe@profihost.ag \
    --cc=cgroups@vger.kernel.org \
    --cc=chris@chrisdown.name \
    --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 \
    /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