From: George Dunlap <George.Dunlap@eu.citrix.com>
To: Andres Lagar-Cavilla <andreslc@gridcentric.ca>
Cc: "Tim (Xen.org)" <tim@xen.org>,
Peter Maloney <peter.maloney@brockmann-consult.de>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: xen-unstable, winxp32 very poor performance on AMD FX-8150, I bisected and changeset is 24770:7f79475d3de7
Date: Mon, 21 Jan 2013 12:07:46 +0000 [thread overview]
Message-ID: <CAFLBxZas9XjQODiXmw+jsQzjjvNKccf1UeW6hy3ozX+=Nt6MDw@mail.gmail.com> (raw)
In-Reply-To: <E78D953B-0860-4FF4-8367-9AD25E638B06@gridcentric.ca>
[-- Attachment #1.1: Type: text/plain, Size: 851 bytes --]
On Fri, Jan 18, 2013 at 2:40 PM, Andres Lagar-Cavilla <
andreslc@gridcentric.ca> wrote:
> I unfortunately don't have AMD hardware to test with. On our regular win7
> EPT-based workloads we've seen no noticeable degradations.
>
> The answer to this one obviously lies in profiling the right sw/hw combo.
>
It seems like given the nature of the work you're doing, having at least a
couple of AMD boxes to test on would make sense. It would be a shame for
your company to lose a big deal because (for example) a potential customer
had just bought 100's of AMD boxes, and your extensions just had terrible
performance on their already-paid-for-and-installed hardware.
I've got a box here that exhibits the behavior (or something like it
anyway), but I probably wouldn't have a chance to look at it until the end
of February at the earliest.
-George
[-- Attachment #1.2: Type: text/html, Size: 1241 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-01-21 12:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-20 17:21 xen-unstable, winxp32 very poor performance on AMD FX-8150, I bisected and changeset is 24770:7f79475d3de7 Peter Maloney
2012-10-20 18:40 ` Peter Maloney
2012-10-22 13:56 ` Andres Lagar-Cavilla
2012-10-22 13:59 ` Tim Deegan
2012-10-23 22:17 ` Peter Maloney
2012-11-01 17:00 ` Tim Deegan
2012-11-01 17:28 ` Andres Lagar-Cavilla
2012-11-13 13:17 ` Peter Maloney
2012-11-22 18:54 ` Peter Maloney
2013-01-12 15:25 ` Peter Maloney
2013-01-17 20:57 ` Pasi Kärkkäinen
2013-01-18 14:22 ` George Dunlap
2013-01-18 14:40 ` Andres Lagar-Cavilla
2013-01-21 12:07 ` George Dunlap [this message]
2013-01-18 14:30 ` George Dunlap
2013-01-26 12:30 ` Peter Maloney
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='CAFLBxZas9XjQODiXmw+jsQzjjvNKccf1UeW6hy3ozX+=Nt6MDw@mail.gmail.com' \
--to=george.dunlap@eu.citrix.com \
--cc=andreslc@gridcentric.ca \
--cc=peter.maloney@brockmann-consult.de \
--cc=tim@xen.org \
--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 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).