From: Andrew Theurer <habanero@linux.vnet.ibm.com>
To: "Nakajima, Jun" <jun.nakajima@intel.com>
Cc: kvm-devel <kvm@vger.kernel.org>
Subject: Re: KVM performance vs. Xen
Date: Wed, 29 Apr 2009 10:33:06 -0500 [thread overview]
Message-ID: <49F87332.4050902@linux.vnet.ibm.com> (raw)
In-Reply-To: <0B53E02A2965CE4F9ADB38B34501A3A17E171DF3@orsmsx505.amr.corp.intel.com>
Nakajima, Jun wrote:
> On 4/29/2009 7:41:50 AM, Andrew Theurer wrote:
>
>> I wanted to share some performance data for KVM and Xen. I thought it
>> would be interesting to share some performance results especially
>> compared to Xen, using a more complex situation like heterogeneous
>> server consolidation.
>>
>> The Workload:
>> The workload is one that simulates a consolidation of servers on to a
>> single host. There are 3 server types: web, imap, and app (j2ee). In
>> addition, there are other "helper" servers which are also
>> consolidated: a db server, which helps out with the app server, and an
>> nfs server, which helps out with the web server (a portion of the docroot is nfs mounted).
>> There is also one other server that is simply idle. All 6 servers
>> make up one set. The first 3 server types are sent requests, which in
>> turn may send requests to the db and nfs helper servers. The request
>> rate is throttled to produce a fixed amount of work. In order to
>> increase utilization on the host, more sets of these servers are used.
>> The clients which send requests also have a response time requirement
>> which is monitored. The following results have passed the response
>> time requirements.
>>
>> The host hardware:
>> A 2 socket, 8 core Nehalem with SMT, and EPT enabled, lots of disks, 4
>> x
>> 1 GB Ethenret
>>
>> The host software:
>> Both Xen and KVM use the same host Linux OS, SLES11. KVM uses the
>> 2.6.27.19-5-default kernel and Xen uses the 2.6.27.19-5-xen kernel. I
>> have tried 2.6.29 for KVM, but results are actually worse. KVM
>> modules are rebuilt with kvm-85. Qemu is also from kvm-85. Xen
>> version is "3.3.1_18546_12-3.1".
>>
>> The guest software:
>> All guests are RedHat 5.3. The same disk images are used but
>> different kernels. Xen uses the RedHat Xen kernel and KVM uses 2.6.29
>> with all paravirt build options enabled. Both use PV I/O drivers. Software used:
>> Apache, PHP, Java, Glassfish, Postgresql, and Dovecot.
>>
>>
>
> Just for clarification. So are you using PV (Xen) Linux on Xen, not HVM? Is that 32-bit or 64-bit?
>
PV, 64-bit.
-Andrew
next prev parent reply other threads:[~2009-04-29 15:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-29 14:41 KVM performance vs. Xen Andrew Theurer
2009-04-29 15:20 ` Nakajima, Jun
2009-04-29 15:33 ` Andrew Theurer [this message]
2009-04-30 8:56 ` Avi Kivity
2009-04-30 12:49 ` Andrew Theurer
2009-04-30 13:02 ` Avi Kivity
2009-04-30 13:44 ` Andrew Theurer
2009-04-30 13:47 ` Anthony Liguori
2009-04-30 13:52 ` Avi Kivity
2009-04-30 13:45 ` Anthony Liguori
2009-04-30 13:53 ` Avi Kivity
2009-04-30 15:08 ` Anthony Liguori
2009-04-30 13:59 ` Avi Kivity
2009-04-30 14:04 ` Andrew Theurer
2009-04-30 15:11 ` Anthony Liguori
2009-04-30 15:19 ` Avi Kivity
2009-04-30 15:59 ` Anthony Liguori
2009-05-01 0:40 ` Andrew Theurer
2009-05-03 16:20 ` Avi Kivity
2009-04-30 15:09 ` Anthony Liguori
2009-04-30 16:41 ` Marcelo Tosatti
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=49F87332.4050902@linux.vnet.ibm.com \
--to=habanero@linux.vnet.ibm.com \
--cc=jun.nakajima@intel.com \
--cc=kvm@vger.kernel.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