From: Alwin Antreich via pve-devel <pve-devel@lists.proxmox.com>
To: pve-devel@lists.proxmox.com
Cc: Alwin Antreich <alwin@antreich.com>
Subject: [pve-devel] [PATCH docs v2 3/3] pveceph: link ceph configure section
Date: Wed, 29 Oct 2025 10:18:11 +0100 [thread overview]
Message-ID: <mailman.364.1761730019.362.pve-devel@lists.proxmox.com> (raw)
In-Reply-To: <20251029091811.2800592-1-alwin@antreich.com>
[-- Attachment #1: Type: message/rfc822, Size: 4546 bytes --]
From: Alwin Antreich <alwin@antreich.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH docs v2 3/3] pveceph: link ceph configure section
Date: Wed, 29 Oct 2025 10:18:11 +0100
Message-ID: <20251029091811.2800592-3-alwin@antreich.com>
to follow how ceph configuration is adjusted
Signed-off-by: Alwin Antreich <alwin@antreich.com>
---
pveceph.adoc | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/pveceph.adoc b/pveceph.adoc
index cefecad..0d6e9ec 100644
--- a/pveceph.adoc
+++ b/pveceph.adoc
@@ -136,8 +136,9 @@ during critical operations, such as recovery, rebalancing, or backfilling. That
means you should avoid maxing out your available memory already on regular
operation, but rather leave some headroom to cope with outages.
-The current recommendation is to configure OSDs with at least **8 GiB of
-memory** for good performance. The OSD daemon requires 4 GiB by default.
+The current recommendation is to xref:pve_ceph_configuration[configure] OSDs
+with at least **8 GiB of memory** for good performance. The OSD daemon requires
+4 GiB by default.
NOTE: Total memory consumption is primarily determined by the number of OSD
daemons. However, for critical operations, all Ceph services may require
--
2.39.5
[-- 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:[~2025-10-29 9:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251029091811.2800592-1-alwin@antreich.com>
2025-10-29 9:18 ` [pve-devel] [PATCH docs v2 2/3] pveceph: add section about ceph configuration Alwin Antreich via pve-devel
2025-10-30 13:29 ` Aaron Lauterer
2025-10-29 9:18 ` Alwin Antreich 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.364.1761730019.362.pve-devel@lists.proxmox.com \
--to=pve-devel@lists.proxmox.com \
--cc=alwin@antreich.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