From: "Shannon Sterz" <s.sterz@proxmox.com>
To: "Maximiliano Sandoval" <m.sandoval@proxmox.com>
Cc: pve-devel@lists.proxmox.com
Subject: Re: [PATCH docs v2 1/2] local-zfs: rephrase ARC limit
Date: Wed, 11 Mar 2026 14:35:04 +0100 [thread overview]
Message-ID: <DGZZQKJBJK7L.24HWCXZ4JGJ35@proxmox.com> (raw)
In-Reply-To: <20260226084639.107816-2-m.sandoval@proxmox.com>
On Thu Feb 26, 2026 at 9:46 AM CET, Maximiliano Sandoval wrote:
> We rephrase the current section putting more emphasis on the current
> state of things given than Proxmox VE 8.1 was released over two years
> ago.
>
> We also document ZFS' default size. See [zfs-6a629f3] for more details.
>
> This also frames the problem for pre-existing setups in its own
> paragraph.
>
> [zfs-6a629f3] https://github.com/openzfs/zfs/commit/6a629f32344468ae81b264055916641480cb438d
>
> Signed-off-by: Maximiliano Sandoval <m.sandoval@proxmox.com>
> ---
> local-zfs.adoc | 13 +++++++++----
> 1 file changed, 9 insertions(+), 4 deletions(-)
>
> diff --git a/local-zfs.adoc b/local-zfs.adoc
> index 85fa092..b3a462d 100644
> --- a/local-zfs.adoc
> +++ b/local-zfs.adoc
> @@ -586,10 +586,15 @@ configured for the root user.
> Limit ZFS Memory Usage
> ~~~~~~~~~~~~~~~~~~~~~~
>
> -ZFS uses '50 %' of the host memory for the **A**daptive **R**eplacement
> -**C**ache (ARC) by default. For new installations starting with {pve} 8.1, the
> -ARC usage limit will be set to '10 %' of the installed physical memory, clamped
> -to a maximum of +16 GiB+. This value is written to `/etc/modprobe.d/zfs.conf`.
> +ZFS uses '10 %' of the host memory, clamped to a maximum of +16 GiB+, for the
> +**A**daptive **R**eplacement **C**ache (ARC) by default. This value is written
> +to `/etc/modprobe.d/zfs.conf` during installation.
> +
> +Before {pve} 8.1, the ARC usage limit was not set during installation and
> +matched ZFS' default value which was either 62.5% starting on ZFS 2.3.0 or 50%
nit: i think "starting with" sounds more natural in english
> +for older versions. For existing installations that predate {pve} 8.1, manual
> +steps would have to be performed in order to lower the usage limit as described
> +below.
>
> Allocating enough memory for the ARC is crucial for IO performance, so reduce it
> with caution. As a general rule of thumb, allocate at least +2 GiB Base + 1
next prev parent reply other threads:[~2026-03-11 13:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 8:46 [PATCH docs v2 0/2] " Maximiliano Sandoval
2026-02-26 8:46 ` [PATCH docs v2 1/2] " Maximiliano Sandoval
2026-03-11 13:35 ` Shannon Sterz [this message]
2026-03-12 13:48 ` Friedrich Weber
2026-02-26 8:46 ` [PATCH docs v2 2/2] local-zfs: add reference to the zfs(4) manual Maximiliano Sandoval
2026-03-11 13:36 ` [PATCH docs v2 0/2] local-zfs: rephrase ARC limit Shannon Sterz
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=DGZZQKJBJK7L.24HWCXZ4JGJ35@proxmox.com \
--to=s.sterz@proxmox.com \
--cc=m.sandoval@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