From: Mike Galbraith <umgwanakikbuti@gmail.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Peter Zijlstra <peterz@infradead.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
LKML <linux-kernel@vger.kernel.org>,
Linux PM list <linux-pm@vger.kernel.org>,
Doug Smythies <dsmythies@telus.net>,
Rik van Riel <riel@redhat.com>
Subject: Re: [regression] cross core scheduling frequency drop bisected to 0c313cb20732
Date: Sun, 10 Apr 2016 16:54:01 +0200 [thread overview]
Message-ID: <1460300041.4383.31.camel@gmail.com> (raw)
In-Reply-To: <1460280912.4251.27.camel@gmail.com>
On Sun, 2016-04-10 at 11:35 +0200, Mike Galbraith wrote:
> On Sun, 2016-04-10 at 05:44 +0200, Rafael J. Wysocki wrote:
> > On Sat, Apr 9, 2016 at 6:39 PM, Mike Galbraith <
> > umgwanakikbuti@gmail.com> wrote:
> > >
> > > Hm, setting gov=performance, and taking the average of 3 30 second
> > > interval PkgWatt samples as pipe-test runs..
> > >
> > > 714KHz/28.03Ws = 25.46
> > > 877KHz/30.28Ws = 28.96
> > >
> > > ..for pipe-test, the tradeoff look a bit more like red than green.
> >
> > Well, fair enough, but that's just pipe-test, and what about the
> > people who don't see the performance gain and see the energy loss,
> > like Doug?
>
> Perhaps Doug sees increased power because he's not throttling no_hz,
> whereas I am, so he burns more power getting _to_ idle? Dunno, maybe
> he'll try the attached. If it's a general case energy loser, so be it,
> numbers talk, bs walks and all that ;-)
And here are the rest of my numbers..
> tbench 1 2 4 8
> base 752 1283 2250 3362
>
> select_idle_sibling() off
> 735 1344 2080 2884
> delta .977 1.047 .924 .857
>
> select_idle_sibling() on, 0c313cb20732 reverted
> 816 1317 2240 3388
> delta 1.085 1.026 .995 1.007 vs base
> delta 1.110 .979 1.076 1.174 vs off
> (^hm)
tbench 2 turboboost off
base 1215 1.00 1215/32.24=37.68
revert 1252 1.03 1252/35.82=34.95=loser
tbench 2 throughput hm is apparently a turboboost oddity, and..
tbench (turboboost back on)
power 1 2 4 8
base 23.88 37.41 54.64 62.25
revert 31.25 42.53 55.11 62.66
MB/s/Ws 1 2 4 8
base 31.49 34.29 41.17 54.00
revert 26.11 30.96 40.64 54.06
..while single pipe-test pair said green/green, tbench numbers say
throughput green, but energy efficiency red across the board.
-Mike
next prev parent reply other threads:[~2016-04-10 14:54 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-08 5:20 [regression] cross core scheduling frequency drop bisected to 0c313cb20732 Mike Galbraith
2016-04-08 6:45 ` Peter Zijlstra
2016-04-08 6:50 ` Mike Galbraith
2016-04-08 20:59 ` Rafael J. Wysocki
2016-04-08 22:19 ` Doug Smythies
2016-04-09 6:44 ` Mike Galbraith
2016-04-09 7:17 ` Doug Smythies
2016-04-09 7:27 ` Mike Galbraith
2016-04-09 11:08 ` Peter Zijlstra
2016-04-09 6:40 ` Mike Galbraith
2016-04-09 12:33 ` Rafael J. Wysocki
2016-04-09 15:10 ` Mike Galbraith
2016-04-09 16:39 ` Mike Galbraith
2016-04-10 3:44 ` Rafael J. Wysocki
2016-04-10 7:16 ` Doug Smythies
2016-04-10 9:35 ` Mike Galbraith
2016-04-10 14:54 ` Mike Galbraith [this message]
2016-04-09 11:07 ` Peter Zijlstra
2016-04-09 12:31 ` Rafael J. Wysocki
2016-04-10 15:39 ` Mike Galbraith
2016-04-10 20:24 ` Rik van Riel
2016-04-11 3:04 ` Mike Galbraith
2016-04-11 12:38 ` Rik van Riel
2016-04-11 13:21 ` Rafael J. Wysocki
2016-04-11 13:38 ` Rik van Riel
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=1460300041.4383.31.camel@gmail.com \
--to=umgwanakikbuti@gmail.com \
--cc=dsmythies@telus.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rafael@kernel.org \
--cc=riel@redhat.com \
--cc=rjw@rjwysocki.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.