From: Mel Gorman <mgorman@techsingularity.net>
To: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>, Jirka Hladky <jhladky@redhat.com>,
Rik van Riel <riel@surriel.com>,
LKML <linux-kernel@vger.kernel.org>,
Linux-MM <linux-mm@kvack.org>
Subject: Re: [PATCH 2/2] mm, numa: Migrate pages to local nodes quicker early in the lifetime of a task
Date: Wed, 3 Oct 2018 14:21:55 +0100 [thread overview]
Message-ID: <20181003132155.GD7003@techsingularity.net> (raw)
In-Reply-To: <20181003130741.GA4488@linux.vnet.ibm.com>
On Wed, Oct 03, 2018 at 06:37:41PM +0530, Srikar Dronamraju wrote:
> * Srikar Dronamraju <srikar@linux.vnet.ibm.com> [2018-10-02 23:00:05]:
>
> > I will try to get a DayTrader run in a day or two. There JVM and db threads
> > act on the same memory, I presume it might show some insights.
>
> I ran 2 runs of daytrader 7 with and without patch on a 2 node power9
> PowerNv box.
> https://github.com/WASdev/sample.daytrader7
> In each run, has 8 JVMs.
>
> Throughputs (Higher are better)
> Without patch 19216.8 18900.7 Average: 19058.75
> With patch 18644.5 18480.9 Average: 18562.70
>
> Difference being -2.6% regression
>
That's unfortunate.
How much does this workload normally vary between runs? If you monitor
migrations over time, is there an increase spike in migration early in
the lifetime of the workload?
--
Mel Gorman
SUSE Labs
next prev parent reply other threads:[~2018-10-03 13:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-01 10:05 [PATCH 0/2] Faster migration for automatic NUMA balancing Mel Gorman
2018-10-01 10:05 ` [PATCH 1/2] mm, numa: Remove rate-limiting of automatic numa balancing migration Mel Gorman
2018-10-01 15:39 ` Rik van Riel
2018-10-02 10:17 ` [tip:sched/urgent] mm, sched/numa: Remove rate-limiting of automatic NUMA " tip-bot for Mel Gorman
2018-10-02 11:54 ` [PATCH 1/2] mm, numa: Remove rate-limiting of automatic numa " Srikar Dronamraju
2018-10-01 10:05 ` [PATCH 2/2] mm, numa: Migrate pages to local nodes quicker early in the lifetime of a task Mel Gorman
2018-10-01 15:41 ` Rik van Riel
2018-10-02 10:17 ` [tip:sched/urgent] sched/numa: " tip-bot for Mel Gorman
2018-10-02 12:41 ` [PATCH 2/2] mm, numa: " Srikar Dronamraju
2018-10-02 13:54 ` Mel Gorman
2018-10-02 17:30 ` Srikar Dronamraju
2018-10-02 18:22 ` Mel Gorman
2018-10-03 13:15 ` Srikar Dronamraju
2018-10-03 13:07 ` Srikar Dronamraju
2018-10-03 13:21 ` Mel Gorman [this message]
2018-10-03 14:08 ` Srikar Dronamraju
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=20181003132155.GD7003@techsingularity.net \
--to=mgorman@techsingularity.net \
--cc=jhladky@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=riel@surriel.com \
--cc=srikar@linux.vnet.ibm.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).