From: Mel Gorman <mgorman@techsingularity.net>
To: Ivan Babrou <ivan@cloudflare.com>
Cc: linux-mm@kvack.org, linux-kernel <linux-kernel@vger.kernel.org>,
kernel-team <kernel-team@cloudflare.com>,
Andrew Morton <akpm@linux-foundation.org>,
Rik van Riel <riel@surriel.com>, Vlastimil Babka <vbabka@suse.cz>
Subject: Re: Reclaim regression after 1c30844d2dfe
Date: Wed, 12 Feb 2020 23:55:25 +0000 [thread overview]
Message-ID: <20200212235525.GU3466@techsingularity.net> (raw)
In-Reply-To: <CABWYdi36O_Gd6=CVZkxY6RR8r4EKzEngScngT5VZc9-x4TB=3w@mail.gmail.com>
On Wed, Feb 12, 2020 at 02:45:39PM -0800, Ivan Babrou wrote:
> Here's a typical graph: https://imgur.com/a/n03x5yH
>
> * Green (numa0) and blue (numa1) for 4.19
> * Yellow (numa0) and orange (numa1) for 5.4
>
> These downward slopes on numa0 on 5.4 are somewhat typical to the
> worst case scenario.
>
> If I try to clean up data a bit from a bunch of machines, this is how
> numa0 compares to numa1 with 1h average values of free memory above
> 5GiB:
>
> * https://imgur.com/a/6T4rRzi
>
> I think it's safe to say that numa0 is much much worse, but I cannot
> be 100% sure that numa1 is free from adverse effects, they may be just
> hiding in the noise caused by rolling reboots.
>
Ok, while I expected node 0 to be worse in general, a runaway boost due
to constant fragmentation would be a problem in general. In either case,
the patch should reduce the damage. Is there any chance that the patch
can be tested or would it be disruptive for you?
--
Mel Gorman
SUSE Labs
next prev parent reply other threads:[~2020-02-12 23:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 22:54 Ivan Babrou
2020-02-07 23:05 ` Rik van Riel
2020-02-08 9:08 ` Vlastimil Babka
2020-02-08 11:11 ` Hillf Danton
2020-02-11 10:16 ` Mel Gorman
2020-02-12 22:45 ` Ivan Babrou
2020-02-12 23:55 ` Mel Gorman [this message]
2020-02-18 22:07 ` Ivan Babrou
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=20200212235525.GU3466@techsingularity.net \
--to=mgorman@techsingularity.net \
--cc=akpm@linux-foundation.org \
--cc=ivan@cloudflare.com \
--cc=kernel-team@cloudflare.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@surriel.com \
--cc=vbabka@suse.cz \
/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