All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Maloney <peter.maloney@brockmann-consult.de>
To: xen-devel@lists.xen.org
Subject: Re: 4.1.2 very slow without upstream patches, but fast with them, also 4.2 very slow
Date: Tue, 07 Aug 2012 09:25:18 +0200	[thread overview]
Message-ID: <5020C2DE.304@brockmann-consult.de> (raw)
In-Reply-To: <501FB9060200007800092D4E@nat28.tlf.novell.com>

> That still won't tell us which patches you did apply.
I applied no patches and tested, and the result was slow. And then
applied all patches, and it was fast. I didn't try figuring out which
one it was.


So I guess I'll try:
- the latest unstable 4.2
- the 4.1.3-rc (Which includes the patch Malcolm suggested)
- and my rpm source with half patches, 3/4 of them, etc. binary search
style to see which patch(es) changed the performance. But this means I
won't be able to narrow it down to a single patch, but only the point in
the long list where the most dramatic change happens, possibly depending
on many previous patches.

Thanks so far, guys.


On 08/06/2012 12:31 PM, Jan Beulich wrote:
>>>> On 06.08.12 at 12:12, Peter Maloney <peter.maloney@brockmann-consult.de> wrote:
>> my AMD FX-8150 system with vanilla source code is super slow, both the
>> dom0 and domUs. However, after I merge the upstream patches I found in
>> the openSUSE rpm, it runs normally.
> I'd be very surprised if you really just took the upstream patches,
> and the result was better than 4.2-rc1. After all, what upstream
> means is that they were taken from -unstable.
>
>> I tried 4.2-unstable and it was the same. There was no rc1 when I tested
>> it about 1.5 weeks ago. And 4.2 has the same horrible performance, and
>> obviously those patches won't work any more since the 4.2 code looks
>> completely reorganized, so I'm stuck with 4.1.2
> Obviously the upstream patches can't be applied to something
> that already has all those changes. Other patches, of which we
> unfortunately have quite a few, would be a different story.
>
>> Here is the rpm I was using at the time:
>> http://download.opensuse.org/update/12.1/src/xen-4.1.2_16-1.7.1.src.rpm 
>>
>> To see the list of the patches and what order to apply them, see the
>> spec file.
> That still won't tell us which patches you did apply.
>
>> Please make sure this performance issue is fixed for the 4.2 release.
>> And I would be happy to test whatever files you send me.
> The sort of report you're doing isn't that helpful. What would
> help is if you could narrow down which patch(es) it is that
> make things so much better. Giving 4.1.3-rc a try might also
> be worthwhile, albeit I would hope we don't have a regression
> in 4.2.0-rc compared to 4.1.3-rc...
>
> Jan
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel


-- 

--------------------------------------------
Peter Maloney
Brockmann Consult
Max-Planck-Str. 2
21502 Geesthacht
Germany
Tel: +49 4152 889 300
Fax: +49 4152 889 333
E-mail: peter.maloney@brockmann-consult.de
Internet: http://www.brockmann-consult.de
--------------------------------------------

  reply	other threads:[~2012-08-07  7:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-06 10:12 4.1.2 very slow without upstream patches, but fast with them, also 4.2 very slow Peter Maloney
2012-08-06 10:24 ` Andrew Cooper
2012-08-06 10:31 ` Jan Beulich
2012-08-07  7:25   ` Peter Maloney [this message]
2012-08-13 18:54     ` Peter Maloney
2012-08-13 20:59       ` Peter Maloney
2012-10-03 17:19         ` Peter Maloney
2012-10-03 20:05           ` Peter Maloney
2012-10-04 14:25             ` Konrad Rzeszutek Wilk
2012-10-05 20:19               ` Peter Maloney
2012-10-06  8:36                 ` Peter Maloney
2012-08-06 12:41 ` Malcolm Crossley
2012-08-06 14:02   ` Konrad Rzeszutek Wilk
     [not found]   ` <20120806140226.GB3093@phenom.dumpdata.com>
2012-08-07 21:42     ` M A Young
     [not found]     ` <alpine.DEB.2.00.1208072239120.8441@vega-c.dur.ac.uk>
2012-08-07 22:21       ` W. Michael Petullo

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=5020C2DE.304@brockmann-consult.de \
    --to=peter.maloney@brockmann-consult.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.