From: "Stefan Sterz" <s.sterz@proxmox.com>
To: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>,
"Fiona Ebner" <f.ebner@proxmox.com>
Subject: Re: [pve-devel] [PATCH docs] system-requirements: mention that SSDs with PLP should be used
Date: Wed, 20 Mar 2024 11:01:50 +0100 [thread overview]
Message-ID: <CZYHOIPEX6H7.2KOAUWT0SKN05@proxmox.com> (raw)
In-Reply-To: <a8ccc082-05ba-44d9-88ad-a0884dc1ac9f@proxmox.com>
On Wed Mar 20, 2024 at 10:49 AM CET, Aaron Lauterer wrote:
>
>
> On 2024-03-20 10:30, Fiona Ebner wrote:
> > Am 20.03.24 um 09:56 schrieb Aaron Lauterer:
> >> Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
> >> ---
> >> pve-system-requirements.adoc | 2 ++
> >> 1 file changed, 2 insertions(+)
> >>
> >> diff --git a/pve-system-requirements.adoc b/pve-system-requirements.adoc
> >> index bc3689d..4db5358 100644
> >> --- a/pve-system-requirements.adoc
> >> +++ b/pve-system-requirements.adoc
> >> @@ -49,6 +49,8 @@ Recommended System Requirements
> >> (BBU) or non-RAID for ZFS and Ceph. Neither ZFS nor Ceph are compatible with a
> >> hardware RAID controller.
> >> ** Shared and distributed storage is possible.
> >> +** SSDs with Power-Loss-Protection (PLP) are recommended for good performance.
> >> + Using consumer SSDs is discouraged.
> >>
> >
> > Having PLP might correlate with having good performance, but it's not
> > the reason for good performance and good performance is not the reason
> > you want PLP. It's just that both things are present in many enterprise
> > SSDs, I'd mention that explicitly to avoid potential confusion.
>
> When it comes to sync writes, it is definitely one reason for the good
> performance ;)
> But yeah, let's think about it, what about the following?:
>
>
> Enterprise grade SSDs are recommended for good performance. Checking for
> Power-Loss-Protection (PLP) is a good way to avoid consumer grade
> SSDs. The use of consumer grade SSDs is discouraged.
>
>
> Not too happy with that either, but phrasing it correctly and succinct
> is an art in itself.
>
How about:
Enterprise SSDs with good performance are recommended.
Power-Loss-Protection (PLP) support can help identify such disks. Using
consumer SSDs is discouraged
> >
> >> * Redundant (Multi-)Gbit NICs, with additional NICs depending on the preferred
> >> storage technology and cluster setup.
>
>
> _______________________________________________
> pve-devel mailing list
> pve-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2024-03-20 10:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-20 8:56 Aaron Lauterer
2024-03-20 9:30 ` Fiona Ebner
2024-03-20 9:49 ` Aaron Lauterer
2024-03-20 10:01 ` Stefan Sterz [this message]
2024-03-20 10:02 ` Fiona Ebner
2024-03-20 14:48 ` Maximiliano Sandoval
2024-03-21 8:06 ` Thomas Lamprecht
2024-03-28 13:29 ` Aaron Lauterer
2024-03-21 10:43 ` Aaron Lauterer
2024-03-29 13:11 ` [pve-devel] applied: " 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=CZYHOIPEX6H7.2KOAUWT0SKN05@proxmox.com \
--to=s.sterz@proxmox.com \
--cc=f.ebner@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