xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@novell.com>
To: Keir Fraser <keir.xen@gmail.com>,
	Juergen Gross <juergen.gross@ts.fujitsu.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Performance difference between Xen versions
Date: Mon, 02 May 2011 08:23:37 +0100	[thread overview]
Message-ID: <4DBE7819020000780003F1B6@vpn.id2.novell.com> (raw)
In-Reply-To: <C9E41092.170DB%keir.xen@gmail.com>

>>> On 02.05.11 at 08:41, Keir Fraser <keir.xen@gmail.com> wrote:
> On 02/05/2011 06:31, "Juergen Gross" <juergen.gross@ts.fujitsu.com> wrote:
> 
>>>> Is there any easy explanation for this? Both Xen versions are from SLES
>>>> (SLES11 or SLES11 SP1).
>>> I think cpufreq handling was off by default in 3.3, and is on by
>>> default on 4.0. Try turning this off, or using the performance
>>> governor.
>> Jan, you got it! With cpufreq=none Xen 4.0 has more or less the same numbers
>> as 3.3. Now I wonder why the default is so much slower. I looks as if the
>> hypervisor would run at a lower speed. I can't believe it should behave like
>> that!
> 
> It runs at lower frequency unless your test offers sufficient load over a
> long enough time period. Short microbenchmarks are probably finished before
> the frequency governor can react.

Correct. I generally found the default threshold of the ondemand
governor nor very suitable for optimal performance of short lived
jobs, and boot all of my systems with "cpufreq=xen:ondemand,threshold=20".

Jan

  reply	other threads:[~2011-05-02  7:23 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-29 12:32 Performance difference between Xen versions Juergen Gross
2011-04-29 13:28 ` Keir Fraser
2011-04-29 13:35   ` Juergen Gross
2011-04-29 14:58     ` Keir Fraser
2011-04-29 16:10 ` Jan Beulich
2011-05-02  5:31   ` Juergen Gross
2011-05-02  6:41     ` Keir Fraser
2011-05-02  7:23       ` Jan Beulich [this message]
2011-05-02  8:00         ` Juergen Gross
2011-05-02  8:15           ` Jan Beulich
2011-05-02  8:23             ` Juergen Gross
2011-05-02  8:49               ` Keir Fraser
2011-05-03  3:06                 ` Tian, Kevin
2011-05-06 13:49                   ` Juergen Gross
2011-05-06 14:27                     ` Jan Beulich
2011-05-11  6:08                     ` Tian, Kevin
2011-05-11  6:23                       ` Juergen Gross
2011-05-02 17:52         ` John Weekes
2011-05-02 18:12           ` Konrad Rzeszutek Wilk
2011-05-02 18:43             ` John Weekes
2011-05-02 19:16               ` John Weekes
2011-05-02 19:36                 ` Konrad Rzeszutek Wilk
2011-05-02 19:54                   ` John Weekes
2011-05-03  2:16                   ` Tian, Kevin
2011-05-03  3:04                 ` Tian, Kevin
2011-05-03  3:39                   ` John Weekes
2011-05-03  7:23                     ` Tian, Kevin
     [not found]         ` <4DBF13BB.3000309@nuclearfallout.net>
2011-05-03  7:23           ` Jan Beulich

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=4DBE7819020000780003F1B6@vpn.id2.novell.com \
    --to=jbeulich@novell.com \
    --cc=juergen.gross@ts.fujitsu.com \
    --cc=keir.xen@gmail.com \
    --cc=xen-devel@lists.xensource.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;
as well as URLs for NNTP newsgroup(s).