qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexandre DERUMIER <aderumier@odiso.com>
To: Kevin Wolf <kwolf@redhat.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 16:53:00 +0100 (CET)	[thread overview]
Message-ID: <b90adba7-d579-44de-86df-a624f13c8779@mailpro> (raw)
In-Reply-To: <50AF8F01.9060008@redhat.com>

>>Can you post more details about your benchmark setup so that this can be 
>>reproduced? And does it reproduce with local files as well or only using 
>>NFS?

Sure, I have redone tests, here the results:
(note that my netapp san have a nvram journal, so directio are as fast than buffered io)

preallocated vs non preallocated have a ratio of 5/1 for local, and 10/1 for nfs.



directio bench
---------------
fio --filename=/dev/vdb --direct=1 -rw=randwrite --bs=4K --size=5G --iodepth=100 --group-reporting --name=file1 --ioengine=libaio

buffered io bench
------------------
fio --filename=/dev/vdb --direct=1 -rw=randwrite --bs=4K --size=5G --iodepth=100 --group-reporting --name=file1 --ioengine=libaio


results
-------
local raw file
---------------
cache=none, directio, 9000 iops
cache=none,  buffered io, 10000 iops

local qcow2 preallocated
--------------------------
cache=none, directio, 8000 iops
cache=none, buffered io, 9000 iops

local qcow2 non preallocated
-----------------------------
cache=none, directio, 1400 iops
cache=none, buffered io, 2000 iops




nfs rawfile (netapp with nvram journal)
----------------------------------------
cache=none, directio, 15000 iops
cache=none,  buffered io, 15000 iops


nfs qcow2 preallocated (netapp with nvram journal)
-------------------
cache=none, directio, 12000 iops
cache=none, buffered io, 12000 iops

nfs qcow2 non preallocated (netapp with nvram journal)
-----------------------------------------------------
cache=none, directio, 1500 iops
cache=none, buffered io, 1500 iops






Alexandre D e rumier

Ingénieur Systèmes et Réseaux


Fixe : 03 20 68 88 85

Fax : 03 20 68 90 88


45 Bvd du Général Leclerc 59100 Roubaix
12 rue Marivaux 75002 Paris


----- Mail original -----

De: "Kevin Wolf" <kwolf@redhat.com>
À: "Alexandre DERUMIER" <aderumier@odiso.com>
Cc: "Dietmar Maurer" <dietmar@proxmox.com>, qemu-devel@nongnu.org
Envoyé: Vendredi 23 Novembre 2012 15:58:09
Objet: Re: [Qemu-devel] qcow2: slow internal snapshot creation

Am 23.11.2012 15:17, schrieb Alexandre DERUMIER:
>>> Preallocation doesn't matter much these days.
>
> I have done benchmark through nfs on a netapp san, (with directio),
>
> I got 300 iops without preallocation, and 6000 iops with preallocation ....

This doesn't sound right, even for writethrough modes.

Can you post more details about your benchmark setup so that this can be
reproduced? And does it reproduce with local files as well or only using
NFS?

Kevin

  reply	other threads:[~2012-11-23 15:53 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
2012-11-23 14:17     ` Alexandre DERUMIER
2012-11-23 14:58       ` Kevin Wolf
2012-11-23 15:53         ` Alexandre DERUMIER [this message]
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=b90adba7-d579-44de-86df-a624f13c8779@mailpro \
    --to=aderumier@odiso.com \
    --cc=dietmar@proxmox.com \
    --cc=kwolf@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).