From: Avi Kivity <avi@redhat.com>
To: Rodrigo Campos <rodrigocc@gmail.com>
Cc: Alexander Atticus <alexander.atticus@gmail.com>,
kvm@vger.kernel.org, Mark McLoughlin <markmc@redhat.com>
Subject: Re: Poor Write I/O Performance on KVM-79
Date: Sun, 04 Jan 2009 21:48:15 +0200 [thread overview]
Message-ID: <4961127F.7020700@redhat.com> (raw)
In-Reply-To: <33d560f70901041007u5d0231dp55b1ef525f2d3925@mail.gmail.com>
Rodrigo Campos wrote:
>> qcow2 will surely lead to miserable performance. raw files are better.
>> best is to use lvm.
>>
>>
>
> What do you mean with best is to use lvm ?
> You just say to use raw images on an lvm partition because you can
> easily resize it ? Or somehow images only use the used space of the
> raw file when used with lvm ? Or there's some trick to make it ?
>
Using lvm directly (-drive file=/dev/vg/volume) is both most efficient
and most reliable, as there are only a small amount of layers involved.
However, you need to commit space in advance (you can grow your volume,
but that takes guest involvement and cannot be done online at the moment).
Using a raw file over a filesystem will be slow since the host
filesystem will be exercised, and due to fragmentation. Raw files only
occupy storage as they are used, but they are difficult to manage
compared to qcow2 files.
Qcow2 files are most flexible, but the least performing.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2009-01-04 19:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-04 6:03 Poor Write I/O Performance on KVM-79 Alexander Atticus
2009-01-04 13:24 ` Avi Kivity
2009-01-04 18:07 ` Rodrigo Campos
2009-01-04 18:48 ` Florent
2009-01-04 19:48 ` Avi Kivity [this message]
2009-01-04 20:12 ` Rodrigo Campos
2009-01-05 14:27 ` Thomas Mueller
2009-01-05 14:30 ` Thomas Mueller
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=4961127F.7020700@redhat.com \
--to=avi@redhat.com \
--cc=alexander.atticus@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=markmc@redhat.com \
--cc=rodrigocc@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox