mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Doug Smythies <dsmythies@telus.net>
Cc: "'Mel Gorman'" <mgorman@techsingularity.net>,
	"'Rafael Wysocki'" <rafael.j.wysocki@intel.com>,
	"'Jörg Otte'" <jrg.otte@gmail.com>,
	"'Linux Kernel Mailing List'" <linux-kernel@vger.kernel.org>,
	"'Linux PM'" <linux-pm@vger.kernel.org>,
	"'Srinivas Pandruvada'" <srinivas.pandruvada@linux.intel.com>
Subject: Re: Performance of low-cpu utilisation benchmark regressed severely since 4.6
Date: Fri, 21 Apr 2017 03:17:39 +0200	[thread overview]
Message-ID: <2640598.7kLQfP2zoQ@aspire.rjw.lan> (raw)
In-Reply-To: <000a01d2b9e6$393afef0$abb0fcd0$@net>

On Thursday, April 20, 2017 07:55:57 AM Doug Smythies wrote:
> On 2017.04.19 01:16 Mel Gorman wrote:
> > On Fri, Apr 14, 2017 at 04:01:40PM -0700, Doug Smythies wrote:
> >> Hi Mel,

[cut]

> > And the revert does help albeit not being an option for reasons Rafael
> > covered.
> 
> New data point: Kernel 4.11-rc7  intel_pstate, powersave forcing the
> load based algorithm: Elapsed 3178 seconds.
> 
> If I understand your data correctly, my load based results are the opposite of yours.
> 
> Mel: 4.11-rc5 vanilla: Elapsed mean: 3750.20 Seconds
> Mel: 4.11-rc5 load based: Elapsed mean: 2503.27 Seconds
> Or: 33.25%
> 
> Doug: 4.11-rc6 stock: Elapsed total (5 runs): 2364.45 Seconds
> Doug: 4.11-rc7 force load based: Elapsed total (5 runs): 3178 Seconds
> Or: -34.4%

I wonder if you can do the same thing I've just advised Mel to do.  That is,
take my linux-next branch:

 git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git linux-next

(which is new material for 4.12 on top of 4.11-rc7) and reduce
INTEL_PSTATE_DEFAULT_SAMPLING_INTERVAL (in intel_pstate.c) in it by 1/2
(force load-based if need be, I'm not sure what PM profile of your test system
is).

Thanks,
Rafael

  reply	other threads:[~2017-04-21  1:23 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-10  8:41 Mel Gorman
2017-04-10 20:51 ` Rafael J. Wysocki
2017-04-11 10:02   ` Mel Gorman
2017-04-21  0:52     ` Rafael J. Wysocki
2017-04-11 15:41   ` Doug Smythies
2017-04-11 16:42     ` Mel Gorman
2017-04-14 23:01     ` Doug Smythies
2017-04-19  8:15       ` Mel Gorman
2017-04-21  1:12         ` Rafael J. Wysocki
2017-04-20 14:55       ` Doug Smythies
2017-04-21  1:17         ` Rafael J. Wysocki [this message]
2017-04-22  6:29         ` Doug Smythies
2017-04-22 21:07           ` Rafael J. Wysocki
2017-04-24 10:01             ` Mel Gorman
2017-04-23 15:31           ` Doug Smythies
2017-04-24  0:59             ` Rafael J. Wysocki
2017-04-24  1:21               ` Srinivas Pandruvada
2017-04-24 14:24               ` Doug Smythies
2017-04-25  7:13               ` Doug Smythies
2017-04-25 21:26                 ` Rafael J. Wysocki
2017-04-25 21:03               ` Doug Smythies

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=2640598.7kLQfP2zoQ@aspire.rjw.lan \
    --to=rjw@rjwysocki.net \
    --cc=dsmythies@telus.net \
    --cc=jrg.otte@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mgorman@techsingularity.net \
    --cc=rafael.j.wysocki@intel.com \
    --cc=srinivas.pandruvada@linux.intel.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

all inboxes | Powered by JetHome®