All of lore.kernel.org
 help / color / mirror / Atom feed
From: mwilck@suse.com (Martin Wilck)
Subject: CPU frequency variations
Date: Tue, 11 Sep 2018 08:55:27 +0200	[thread overview]
Message-ID: <830fa5e6db6e7ba24a81eea4a18be8a1379b7be6.camel@suse.com> (raw)
In-Reply-To: <CA+1E3rLFED9UqDM2GmFMfr935KwjgpLvNauwpnHLz0nwnVrkTw@mail.gmail.com>

On Tue, 2018-09-11@00:02 +0530, Joshi wrote:
> While doing some I/O polling related experiments/optimization, I felt
> the need to eliminate fluctuations (in I/O performance) caused by CPU
> frequency variations.
> 
> During benchmarks (and I mean storage ones), in order to keep running
> CPU at nearly constant high frequency, I tried
> things such as - performance governor, bios-based performance
> settings, explicit setting of sysfs cpu scaling max counters, kernel
> parameters to disable cpufreq etc.
> Some of above helped; On machines with less number of CPUs. While
> nothing seems to help on relatively heavyweight machines.
> Such as on this-  Intel Xeon E5-2690 v3 @2.6 GHz, 2 NUMA nodes, 24
> cpus each.
> 
> Often storage-benchmark seem to suffer because there are more number
> of CPUs available; Binding it to single/few CPUs help in seeing
> better
> numbers.
> 
> May I know how you deal with CPU frequency variations during
> benchmarks.

Are you certain that it's frequency variations that hurt you? Maybe
your CPUs go to deep sleep states? Have you tried e.g.
"intel_idle.max_cstate=0"?

Martin

-- 
Dr. Martin Wilck <mwilck at suse.com>, Tel. +49 (0)911 74053 2107
SUSE Linux GmbH, GF: Felix Imend?rffer, Jane Smithard, Graham Norton
HRB 21284 (AG N?rnberg)

      parent reply	other threads:[~2018-09-11  6:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-10 18:32 CPU frequency variations Joshi
2018-09-10 19:00 ` Keith Busch
2018-09-11  6:55 ` Martin Wilck [this message]

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=830fa5e6db6e7ba24a81eea4a18be8a1379b7be6.camel@suse.com \
    --to=mwilck@suse.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 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.