All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Andreas Kinzler <ml-ak@posteo.de>, xen-devel@lists.xen.org
Subject: Re: serious performance regression in Xen 4.2.4 and 4.2.5
Date: Thu, 19 Feb 2015 11:20:35 +0000	[thread overview]
Message-ID: <54E5C703.7080703@citrix.com> (raw)
In-Reply-To: <54E5C421.2060109@posteo.de>

On 19/02/15 11:08, Andreas Kinzler wrote:
> Hello Xen developers,
>
> since we use Xen for our production systems, I run many tests on Xen
> (stability/performance). One test now uncovered a serious performance
> regression when updating from Xen 4.2.3 to 4.2.x (with x>=4). To
> reproduce run a domU (HVM) and compile a kernel for example ("time
> make -j3"). Below are my results - compilation times more than double!
>
> Is it my mistake or otherwise how could such a bug be unnoticed?
> Really wondering.
> If it is really a regression, will it be fixed since the 4.2 branch is
> declared unsupported?
>
> Regards Andreas
>
> Xen 4.2.3, 3.10.44-el7-pvops0-ak3, Xeon E3-1230, compile in HVM
>     real    2m58.371s
>     user    5m11.580s
>     sys     0m12.736s
>
> Xen 4.2.4, 3.10.44-el7-pvops0-ak3, Xeon E3-1230, compile in HVM
>     real    6m44.697s    (!!!)
>     user    12m4.988s
>     sys     0m33.916s
>
> Xen 4.2.5, 3.10.44-el7-pvops0-ak3, Xeon E3-1230, compile in HVM
>     real    6m27.998s    (!!!)
>     user    11m42.664s
>     sys     0m32.700s
>
>

Is it perhaps
http://xenbits.xen.org/gitweb/?p=xen.git;a=commitdiff;h=f1e0df14412ccc6933a68eda66ac5b7d89186b62
?

There are a number of correctness fixes in that range which will
adversely affect performance.

~Andrew

  reply	other threads:[~2015-02-19 11:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-19 11:08 serious performance regression in Xen 4.2.4 and 4.2.5 Andreas Kinzler
2015-02-19 11:20 ` Andrew Cooper [this message]
2015-02-19 16:24   ` Andreas Kinzler
2015-02-19 13:08 ` Malcolm Crossley
2015-02-19 14:21   ` Jan Beulich
2015-02-19 14:26     ` Malcolm Crossley

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=54E5C703.7080703@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=ml-ak@posteo.de \
    --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.