From: Matthias Heiserer <m.heiserer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs 7/9] local-zfs: rephrase ZFS RAID description
Date: Fri, 18 Nov 2022 12:09:47 +0100 [thread overview]
Message-ID: <20221118110949.59298-7-m.heiserer@proxmox.com> (raw)
In-Reply-To: <20221118110949.59298-1-m.heiserer@proxmox.com>
I tried to make the performance impact clearer, as what "behave like a number of disks"
actually means wasn't quite clear to me.
Use "in regard to" rather than "in regard of", as I couldn't find
any source that this phrase is (commonly) used in modern english.
Signed-off-by: Matthias Heiserer <m.heiserer@proxmox.com>
---
local-zfs.adoc | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/local-zfs.adoc b/local-zfs.adoc
index 6afc110..0fa06b0 100644
--- a/local-zfs.adoc
+++ b/local-zfs.adoc
@@ -167,17 +167,17 @@ Each `vdev` type has different performance behaviors. The two
parameters of interest are the IOPS (Input/Output Operations per Second) and
the bandwidth with which data can be written or read.
-A 'mirror' vdev (RAID1) will approximately behave like a single disk in regards
-to both parameters when writing data. When reading data if will behave like the
-number of disks in the mirror.
+A 'mirror' vdev (RAID1) will approximately behave like a single disk in regard
+to both parameters when writing data. When reading data the performance will
+scale linearly with the number of disks in the mirror.
A common situation is to have 4 disks. When setting it up as 2 mirror vdevs
(RAID10) the pool will have the write characteristics as two single disks in
-regard of IOPS and bandwidth. For read operations it will resemble 4 single
+regard to IOPS and bandwidth. For read operations it will resemble 4 single
disks.
A 'RAIDZ' of any redundancy level will approximately behave like a single disk
-in regard of IOPS with a lot of bandwidth. How much bandwidth depends on the
+in regard to IOPS with a lot of bandwidth. How much bandwidth depends on the
size of the RAIDZ vdev and the redundancy level.
For running VMs, IOPS is the more important metric in most situations.
--
2.30.2
next prev parent reply other threads:[~2022-11-18 11:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 11:09 [pve-devel] [PATCH docs 1/9] bibliography: update 404 link Matthias Heiserer
2022-11-18 11:09 ` [pve-devel] [PATCH docs 2/9] package-repos: fix typos Matthias Heiserer
2022-11-18 11:09 ` [pve-devel] [PATCH docs 3/9] network: fix typo Matthias Heiserer
2022-11-18 11:09 ` [pve-devel] [PATCH docs 4/9] network: fix dead link Matthias Heiserer
2022-11-18 11:09 ` [pve-devel] [PATCH docs 5/9] local-lvm: typo fix/better phrasing Matthias Heiserer
2022-11-18 11:09 ` [pve-devel] [PATCH docs 6/9] local-zfs Remove SSD suggestion as it's outdated Matthias Heiserer
2022-11-18 11:09 ` Matthias Heiserer [this message]
2022-11-18 11:09 ` [pve-devel] [PATCH docs 8/9] local-zfs: typo fix/better phrasing Matthias Heiserer
2022-11-18 11:09 ` [pve-devel] [PATCH docs 9/9] Update ExtJS version Matthias Heiserer
2022-11-18 12:03 ` [pve-devel] [PATCH docs 1/9] bibliography: update 404 link Thomas Lamprecht
2022-11-18 12:04 ` [pve-devel] applied-series: " Thomas Lamprecht
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=20221118110949.59298-7-m.heiserer@proxmox.com \
--to=m.heiserer@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