All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@eu.citrix.com>
To: Dario Faggioli <dario.faggioli@citrix.com>
Cc: Juergen Gross <juergen.gross@ts.fujitsu.com>,
	Massimo Canonico <mex@di.unipmn.it>,
	xen-devel@lists.xen.org
Subject: Re: CAP and performance problem
Date: Thu, 6 Jun 2013 17:27:12 +0100	[thread overview]
Message-ID: <51B0B860.1050703@eu.citrix.com> (raw)
In-Reply-To: <1370534091.17802.10.camel@Solace>

On 06/06/13 16:54, Dario Faggioli wrote:
> On gio, 2013-06-06 at 17:42 +0200, Dario Faggioli wrote:
>> Jokes apart, we may want to add a line there, perhaps on the Wiki, but I
>> honestly don't think this is by any means the cap mechanism's. :-)
>                                                                 ^fault
>
> What I meant is: I don't think this can be considered cap's fault.

It's certainly not cap's fault, but it wouldn't hurt to just put a 
comment saying something like,

"NB that many systems have features that will scale down the computing 
power of a cpu that is not 100% utilized.  This can be in the operating 
system, but can also sometimes be below the operating system in the 
BIOS.  If you set a cap such that individual cores are running at less 
than 100%, this may have an impact on the performance of your workload 
over and above the impact of the cap. For example, a workload that may 
take 300s with a cap of 100% may take 900s with a cap of 50%, because in 
addition to being run only 50% of the time, the cpu is running in a 
lower state and so the 50% you get is less powerful.  If this is a 
problem, look at performance and cpufreq options in our operating system 
and your BIOS."

  -George

  reply	other threads:[~2013-06-06 16:27 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-21  9:02 CAP and performance problem Massimo Canonico
2013-05-21 10:41 ` George Dunlap
2013-05-21 10:48   ` George Dunlap
2013-05-21 11:54     ` Massimo Canonico
2013-05-21 13:06       ` Dario Faggioli
2013-05-21 14:28         ` Massimo Canonico
2013-05-21 14:47           ` Dario Faggioli
2013-05-21 15:26             ` Massimo Canonico
2013-05-22 14:42             ` Massimo Canonico
2013-05-22 15:39               ` Dario Faggioli
2013-05-24  7:48                 ` Massimo Canonico
2013-06-04 14:03                   ` Massimo Canonico
2013-06-04 14:25                     ` Dario Faggioli
2013-06-05 16:50 ` Dario Faggioli
2013-06-05 17:11   ` Dario Faggioli
2013-06-05 17:05     ` Massimo Canonico
2013-06-06  8:37       ` Dario Faggioli
2013-06-06  8:57         ` Massimo Canonico
2013-06-06  9:52           ` Dario Faggioli
2013-06-06 10:39           ` Juergen Gross
2013-06-06 10:44             ` George Dunlap
2013-06-06 12:52               ` Massimo Canonico
2013-06-06 12:58                 ` George Dunlap
2013-06-06 13:02                 ` Juergen Gross
2013-06-06 13:55                   ` Massimo Canonico
2013-06-06 14:12                     ` George Dunlap
2013-06-06 14:12                     ` Dario Faggioli
2013-06-06 15:27                       ` Massimo Canonico
2013-06-06 15:42                         ` Dario Faggioli
2013-06-06 15:54                           ` Dario Faggioli
2013-06-06 16:27                             ` George Dunlap [this message]
2013-06-07  7:40                               ` Massimo Canonico
2013-06-07  4:45                       ` Juergen Gross
2013-06-06 13:03                 ` Dario Faggioli
2013-06-06 13:09                   ` Massimo Canonico
2013-06-06  9:02   ` George Dunlap
2013-06-06  9:48     ` Dario Faggioli

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=51B0B860.1050703@eu.citrix.com \
    --to=george.dunlap@eu.citrix.com \
    --cc=dario.faggioli@citrix.com \
    --cc=juergen.gross@ts.fujitsu.com \
    --cc=mex@di.unipmn.it \
    --cc=xen-devel@lists.xen.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 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.