From: Mel Gorman <mgorman@techsingularity.net>
To: Phil Auld <pauld@redhat.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Valentin Schneider <valentin.schneider@arm.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] sched/fair: Age the average idle time
Date: Thu, 17 Jun 2021 16:40:06 +0100 [thread overview]
Message-ID: <20210617154006.GQ30378@techsingularity.net> (raw)
In-Reply-To: <YMtjvF0en9NjIspl@lorien.usersys.redhat.com>
On Thu, Jun 17, 2021 at 11:01:16AM -0400, Phil Auld wrote:
> > Thanks, so far no serious objection :)
> >
> > The latest results as I see them have been copied to
> > https://beta.suse.com/private/mgorman/melt/v5.13-rc5/3-perf-test/sched/sched-avgidle-v1r6/html/dashboard.html
> > They will move from here if the patch is accepted to 5-assembly replacing
> > 3-perf-test. This naming is part of my workflow for evaluating topic
> > branches separetly and then putting them together for another round
> > of testing.
> >
> > NAS shows small differences but NAS would see limited impact from the
> > patch. Specjbb shows small losses and some minor gains which is unfortunate
> > but the workload tends to see small gains and losses all the time.
> > redis is a mixed bag but has some wins. hackbench is the main benefit
> > because it's wakeup intensive and tends to overload machines where deep
> > searches hurt.
> >
> > There are other results in there if you feel like digging around
> > such as sched-core tested with no processes getting tagged with prctl
> > https://beta.suse.com/private/mgorman/melt/v5.13-rc5/5-assembly/sched/sched-schedcore-v1r2/html/dashboard.html
> >
>
> Thanks for the links. It's cool to see what your results dashboard looks like.
> It's really small, what are you plotting in those heat maps?
>
> It's hard for me to publish the results that come from our testing (web based
> on intranet) but we don't see any major differences with this patch. There
> are some gains here and there mostly balanced by some loses. Overall it comes
> out basically as a wash across our main performance test workload.
>
Ok, that's unfortunate. It's also somewhat surprising but then again, I
don't know what tests were executed.
> It'll be interesting to see if it effects a sensitive, proprietary perf test
> suite from a European company with a 3 letter name :)
>
I don't think it's worth the effort if it's failing microbenchmarks at
the moment.
--
Mel Gorman
SUSE Labs
next prev parent reply other threads:[~2021-06-17 15:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-15 11:16 [PATCH v2] sched/fair: Age the average idle time Mel Gorman
2021-06-15 20:42 ` Peter Zijlstra
2021-06-15 21:13 ` Phil Auld
2021-06-16 9:03 ` Mel Gorman
2021-06-17 15:01 ` Phil Auld
2021-06-17 15:40 ` Mel Gorman [this message]
2021-06-18 19:22 ` Phil Auld
2021-06-16 15:52 ` Vincent Guittot
2021-06-17 7:44 ` Mel Gorman
2021-06-17 8:30 ` Vincent Guittot
2021-06-17 9:40 ` Mel Gorman
2021-06-17 10:02 ` Vincent Guittot
2021-06-17 11:05 ` Mel Gorman
2021-06-17 15:03 ` Vincent Guittot
2021-06-17 15:47 ` Mel Gorman
2021-06-17 16:05 ` Vincent Guittot
2021-06-18 8:46 ` [tip: sched/core] " tip-bot2 for Peter Zijlstra
2021-06-23 14:46 ` [sched/fair] 5359f5ca0f: phoronix-test-suite.stress-ng.SystemVMessagePassing.bogo_ops_s 77.9% improvement kernel test robot
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=20210617154006.GQ30378@techsingularity.net \
--to=mgorman@techsingularity.net \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pauld@redhat.com \
--cc=peterz@infradead.org \
--cc=valentin.schneider@arm.com \
--cc=vincent.guittot@linaro.org \
/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).