From: "DERUMIER, Alexandre via pve-devel" <pve-devel@lists.proxmox.com>
To: "pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>,
"f.ebner@proxmox.com" <f.ebner@proxmox.com>
Cc: "DERUMIER, Alexandre" <alexandre.derumier@groupe-cyllene.com>
Subject: Re: [pve-devel] qcow2 internal snapshot: 4k write speed reduce to 100~200 iops on ssd ?
Date: Thu, 19 Sep 2024 13:50:41 +0000 [thread overview]
Message-ID: <mailman.20.1726753883.332.pve-devel@lists.proxmox.com> (raw)
In-Reply-To: <6a44716a-88bc-4523-b210-d67031917d8f@proxmox.com>
[-- Attachment #1: Type: message/rfc822, Size: 15671 bytes --]
From: "DERUMIER, Alexandre" <alexandre.derumier@groupe-cyllene.com>
To: "pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>, "f.ebner@proxmox.com" <f.ebner@proxmox.com>
Subject: Re: [pve-devel] qcow2 internal snapshot: 4k write speed reduce to 100~200 iops on ssd ?
Date: Thu, 19 Sep 2024 13:50:41 +0000
Message-ID: <a58e0f18bd41976deed2e7177a9d1d26956f06e6.camel@groupe-cyllene.com>
>>Hi,
Hi Fiona,
sorry I didn't see your response.
>>Is the performance drop also this big with the local storage?
yes. (The result is even worst on nfs, or gfs/ocfs2)
>>A performance drop is of course expected, because AFAIU it needs to
>>do
>>COW for the sectors that the snapshot references, but the drop does
>>sound rather dramatic in your case. The performance should be better
>>again once the COW is done, e.g. when running another test
>>afterwards. I
>>quickly tested in a nested VM with qcow2 disk on a directory storage
and
>>--numjobs=4:²
>>
>>ran test, got ~33k IOPS
>>made a snapshot
>>ran test, got ~20k IOPS (it starts out very slow and then recovers)
>>ran test, got ~33k IOPS again
>>
I have tested with another server, I around 60k write and going down
to 600~1000k iops max when a snapshot is token.
I need to increase slowing after some time, maybe 2~3min to get 20k
iops
and 7~10min to get 50kiops again
I'm testing with a 100gb disk
Maybe is is related to metadatas preallocation ? (I'm not sure, but
when you have a new snapshot, the preallocated metadatas are not using
anymore ?)
Anyway, I just send patch for external qcow2 snapshot :)
If somebody have time to review it ^_^
Thanks again for your response !
> is it expected ?
>
> (I don't have use qcow2 snapshot since 10year, so I really don't
> remember performance).
>
Best Regards,
Fiona
>
> Using external snapshot file, I'm around 10000iops.
>
> test inside the vm:
>
> fio --filename=/dev/sdX --ioengine=libaio --direct 1 --bs=4k --
> rw=randwrite --numjobs=64
>
>
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2024-09-19 13:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-30 16:01 DERUMIER, Alexandre via pve-devel
2024-09-11 9:11 ` Fiona Ebner
2024-09-19 13:50 ` DERUMIER, Alexandre via pve-devel [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=mailman.20.1726753883.332.pve-devel@lists.proxmox.com \
--to=pve-devel@lists.proxmox.com \
--cc=alexandre.derumier@groupe-cyllene.com \
--cc=f.ebner@proxmox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal