From: Folke Gleumes <f.gleumes@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs] zfs: add a note about dRaid performance
Date: Wed, 20 Mar 2024 16:52:19 +0100 [thread overview]
Message-ID: <20240320155219.509745-1-f.gleumes@proxmox.com> (raw)
Based on statements from the openZFS documentation where it is described
as providing "the same level of redundancy and performance as raidz" [0].
[0] https://openzfs.github.io/openzfs-docs/Basic%20Concepts/dRAID%20Howto.html
---
local-zfs.adoc | 2 ++
1 file changed, 2 insertions(+)
diff --git a/local-zfs.adoc b/local-zfs.adoc
index a1a14e4..5db94cc 100644
--- a/local-zfs.adoc
+++ b/local-zfs.adoc
@@ -180,6 +180,8 @@ A 'RAIDZ' of any redundancy level will approximately behave like a single disk
in regard to IOPS with a lot of bandwidth. How much bandwidth depends on the
size of the RAIDZ vdev and the redundancy level.
+A 'dRAID' should match the performance of an equivalent 'RAIDZ' pool.
+
For running VMs, IOPS is the more important metric in most situations.
--
2.39.2
next reply other threads:[~2024-03-20 15:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-20 15:52 Folke Gleumes [this message]
2024-03-20 16:12 ` [pve-devel] applied: " Aaron Lauterer
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=20240320155219.509745-1-f.gleumes@proxmox.com \
--to=f.gleumes@proxmox.com \
--cc=pve-devel@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox