public inbox for pmg-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Dominik Csapak <d.csapak@proxmox.com>
To: pmg-devel@lists.proxmox.com
Subject: [pmg-devel] [PATCH pmg-docs v2 2/2] bump recommended memory requriements
Date: Wed, 26 Feb 2025 16:35:52 +0100	[thread overview]
Message-ID: <20250226153552.3788236-2-d.csapak@proxmox.com> (raw)
In-Reply-To: <20250226153552.3788236-1-d.csapak@proxmox.com>

An installation with ZFS, additional signatures, or extra antivirus
software needs probably a bit more than 4 GiB to run well, so bump the
recommendation to 5 GiB to cover such installations.

Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
---
new in v2 because i wasn't sure if we want it. This way it's easier
to apply the patches separately.

 pmg-planning-deployment.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/pmg-planning-deployment.adoc b/pmg-planning-deployment.adoc
index 9c81069..134c593 100644
--- a/pmg-planning-deployment.adoc
+++ b/pmg-planning-deployment.adoc
@@ -128,7 +128,7 @@ Recommended System Requirements
 * Multi-core CPU: 64bit (Intel 64 or AMD64), +
 ** for use in a virtual machine, activate Intel VT/AMD-V CPU flag
 
-* 4 GiB RAM
+* 5 GiB RAM
 
 * Bootable CD-ROM-drive or USB boot support
 
-- 
2.39.5



_______________________________________________
pmg-devel mailing list
pmg-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pmg-devel


  reply	other threads:[~2025-02-26 15:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-26 15:35 [pmg-devel] [PATCH pmg-docs v2 1/2] bump minimum memory requirement Dominik Csapak
2025-02-26 15:35 ` Dominik Csapak [this message]
2025-02-26 15:40   ` [pmg-devel] [PATCH pmg-docs v2 2/2] bump recommended memory requriements Thomas Lamprecht
2025-02-26 15:43 ` [pmg-devel] applied: [PATCH pmg-docs v2 1/2] bump minimum memory requirement 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=20250226153552.3788236-2-d.csapak@proxmox.com \
    --to=d.csapak@proxmox.com \
    --cc=pmg-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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal