From: Anthony Liguori <aliguori@linux.vnet.ibm.com>
To: Nicholas Lee <emptysands@gmail.com>
Cc: Xen development list <xen-devel@lists.xensource.com>
Subject: Re: A Performance Comparison of Hypervisors
Date: Sat, 03 Feb 2007 10:14:56 -0600 [thread overview]
Message-ID: <45C4B500.6000304@linux.vnet.ibm.com> (raw)
In-Reply-To: <2b6116b30702030134j762eed51ud48dc9567d904e97@mail.gmail.com>
Nicholas Lee wrote:
> Obviously not a very fair comparison [1]. I can't see how this was
> done well at all.
I wonder why you say this. I thought the benchmark was done very well.
What we need is more benchmarking, not less. Unfortunately, VMware
makes publishing benchmarks difficult as you have to get their approval.
This benchmark tells us something, the question is what does it tell
us. Let's take a look at the benchmarks they choose. SPECcpu2000 and
SPECjbb2005 are two favorite benchmarks of virtualization vendors. They
are favorites because everyone does well under them :-) Both aren't
sensitive to PTE update or context switch latency and don't involve IO
very much. Even QEMU wouldn't look so bad against these :-)
I'm not familiar with Passmark, but it looks like it's mostly CPU
bound. For all of these virtualization friendly workloads, Xen does
pretty well compared to VMware. For some of the Passmark bits, Xen
actually inches out VMware. Considering we're Open Source, they really
have no excuse to ever be slower than we are :-)
The compile workload was, IMHO, the most serious of the benchmarks.
VMware walloped us on that one. I suspect that's a some shadow paging
overhead and perhaps some disk IO overhead.
The Netperf results are a tad silly. They choose Win2k3 for the guest
OS. They installed a paravirtual network driver in their guest
(vmxnet). However, since no PV network driver is available for Windows
for Xen 3.0.3, they used emulated IO[1]. Of course performance is going
to suck.
I would have rather seen the benchmarks done with a Linux guest using
the PV drivers that are in the tree.
The only embarrassing part is that they weren't able to boot a Win2k3
guest with SMP support. I suspect we need either more QA for HVM or a
better statement of supported guest confirmations.
Regards,
Anthony Liguori
[1] The PV drivers that come in XenEnterprise are, AFAIK, only for
XenEnterprise.
> VMWare are a bit silly to release stuff like this, just lowers the
> whole game.
>
>
> [1] http://www.vmware.com/vmtn/resources/711
> ------------------------------------------------------------------------
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
next prev parent reply other threads:[~2007-02-03 16:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-03 9:34 A Performance Comparison of Hypervisors Nicholas Lee
2007-02-03 16:14 ` Anthony Liguori [this message]
2007-02-04 10:36 ` Nicholas Lee
2007-02-05 5:08 ` Mark Williamson
2007-02-07 0:25 ` Nicholas Lee
2007-02-06 10:55 ` Petersson, Mats
2007-02-05 12:58 ` Henning Sprang
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=45C4B500.6000304@linux.vnet.ibm.com \
--to=aliguori@linux.vnet.ibm.com \
--cc=emptysands@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 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.