public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Ryan Harper <ryanh@us.ibm.com>
To: Arne Kepp <ak@opengeo.org>
Cc: kvm@vger.kernel.org
Subject: Re: Poor write- and overall performance
Date: Fri, 19 Dec 2008 23:19:00 -0600	[thread overview]
Message-ID: <20081220051900.GY13481@us.ibm.com> (raw)
In-Reply-To: <494C4DF7.30106@opengeo.org>

* Arne Kepp <ak@opengeo.org> [2008-12-19 19:45]:
> Avi Kivity wrote:
> >Arne Kepp wrote:
> >>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.
> >
> >I suggest trying scsi in kvm-81, or setting cache=writeback if you 
> >want to keep using IDE (but be aware of the potential for severe data 
> >loss with the latter option).
> >
> 
> Thanks for the tip. I tested with the SCSI driver and 81, unfortunately 
> write performance was approximately the same as before.

Yeah, currently the scsi emulation doesn't queue up writes, rather it
waits for each one to complete which means one cannot take advantage of
the aio infrastructure.  I'm currently working on fixing this; stay tuned.

-- 
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
ryanh@us.ibm.com

      reply	other threads:[~2008-12-20  5:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-14 23:44 Poor write- and overall performance Arne Kepp
2008-12-15  6:38 ` 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 [this message]

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=20081220051900.GY13481@us.ibm.com \
    --to=ryanh@us.ibm.com \
    --cc=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