From: Kevin Wolf <kwolf@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: Avi Kivity <avi@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qcow2: Order concurrent AIO requests on the same unallocated cluster
Date: Tue, 01 Sep 2009 14:29:14 +0200 [thread overview]
Message-ID: <4A9D139A.4050709@redhat.com> (raw)
In-Reply-To: <20090901112647.GZ30093@redhat.com>
Gleb Natapov schrieb:
>>> No really detailed numbers. Installation time for RHEL on qcow2/virtio
>>> went down from 34 min to 19 min, though.
>> That's very impressive. cache=none or cache=wt?
>>
> And how it compares with raw?
I just ran another installation on raw and it took about 16:30 min.
And with the next patch series that I'm going to send today we'll be in
the same region with qcow2.
Kevin
next prev parent reply other threads:[~2009-09-01 12:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-31 14:48 [Qemu-devel] [PATCH] qcow2: Order concurrent AIO requests on the same unallocated cluster Kevin Wolf
2009-09-01 10:19 ` Avi Kivity
2009-09-01 10:50 ` Kevin Wolf
2009-09-01 11:24 ` Avi Kivity
2009-09-01 11:26 ` Gleb Natapov
2009-09-01 12:29 ` Kevin Wolf [this message]
2009-09-01 12:53 ` Avi Kivity
2009-09-01 13:15 ` Kevin Wolf
2009-09-01 11:43 ` Kevin Wolf
2009-09-01 11:55 ` Avi Kivity
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=4A9D139A.4050709@redhat.com \
--to=kwolf@redhat.com \
--cc=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).