public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Arne Kepp <ak@opengeo.org>
To: kvm@vger.kernel.org
Subject: Poor write- and overall performance
Date: Mon, 15 Dec 2008 00:44:17 +0100	[thread overview]
Message-ID: <49459A51.7040905@opengeo.org> (raw)

Hi,

I'm testing KVM 80 (prepackaged from lfarkas.org) on CentOS 5.2 (both 
guest and host) and comparing against Xen 3.3.0. The only modification 
I've really made is that I've set noatime on both guest and host. The 
guest is running straight from an LVM volume and is assigned 4 Gb RAM 
and 4 virtual CPUs.

KVM does well reading from disk (300 Mbyte/s according to IOZone, 
virtually the same as native) and computational tasks like OpenSSL 
signing.  But writing ends up at 30 Mbyte/s (native does 150 Mbyte/s) 
and kernel compilation times are roughly double that of native. KVM 79 
exhibited the same behavior for disk IO, but froze while compiling the 
kernel.

So, short of using the virtio drivers (which I think would require a 
custom kernel since RHEL 5.2 uses 2.6.18), are there any easy tweaks I 
should try to make KVM fare better ?

The host is quad core Intel with 8 Gb RAM and a SAS RAID 5 
configuration. Let me know if you'd like to see the results here.

Sincerely,
-Arne

-- 
Arne Kepp
OpenGeo - http://opengeo.org
Expert service straight from the developers


             reply	other threads:[~2008-12-14 23:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-14 23:44 Arne Kepp [this message]
2008-12-15  6:38 ` Poor write- and overall performance Avi Kivity
2008-12-15 10:22   ` Henrik Holst
2008-12-15 10:26     ` Avi Kivity
2008-12-15 10:29       ` Henrik Holst
2008-12-20  1:44   ` Arne Kepp
2008-12-20  5:19     ` Ryan Harper

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=49459A51.7040905@opengeo.org \
    --to=ak@opengeo.org \
    --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