From: Kevin Wolf <kwolf@redhat.com>
To: Alexandre DERUMIER <aderumier@odiso.com>
Cc: Dietmar Maurer <dietmar@proxmox.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qcow2: slow internal snapshot creation
Date: Fri, 23 Nov 2012 15:09:15 +0100 [thread overview]
Message-ID: <50AF838B.5010703@redhat.com> (raw)
In-Reply-To: <abb9ca41-d531-4e98-abf6-db44528be841@mailpro>
Am 23.11.2012 15:03, schrieb Alexandre DERUMIER:
> performance is also reduced when snapshot exist. (like if they are no preallocated metadatas)
Preallocation doesn't matter much these days.
> see initial git commit
>
> http://git.qemu.org/?p=qemu.git;a=commit;h=a35e1c177debb01240243bd656caca302410d38c
> "qcow2: Metadata preallocation
>
> This introduces a qemu-img create option for qcow2 which allows the metadata to
> be preallocated, i.e. clusters are reserved in the refcount table and L1/L2
> tables, but no data is written to them. Metadata is quite small, so this
> happens in almost no time.
>
> Especially with qcow2 on virtio this helps to gain a bit of performance during
> the initial writes. However, as soon as create a snapshot, we're back to the
> normal slow speed, obviously. So this isn't the real fix, but kind of a cheat
> while we're still having trouble with qcow2 on virtio."
This is a commit message from 2009 that already says that this wasn't
the final solution.
Kevin
next prev parent reply other threads:[~2012-11-23 14:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-23 7:26 [Qemu-devel] qcow2: slow internal snapshot creation Dietmar Maurer
2012-11-23 14:03 ` Alexandre DERUMIER
2012-11-23 14:09 ` Kevin Wolf [this message]
2012-11-23 14:17 ` Alexandre DERUMIER
2012-11-23 14:58 ` Kevin Wolf
2012-11-23 15:53 ` Alexandre DERUMIER
2012-11-23 15:31 ` Kevin Wolf
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=50AF838B.5010703@redhat.com \
--to=kwolf@redhat.com \
--cc=aderumier@odiso.com \
--cc=dietmar@proxmox.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).