From: Maximiliano Sandoval <m.sandoval@proxmox.com>
To: "Shannon Sterz" <s.sterz@proxmox.com>
Cc: pve-devel@lists.proxmox.com
Subject: superseded: [PATCH docs 1/2] local-zfs: Rephrase ARC limit
Date: Thu, 26 Feb 2026 09:51:49 +0100 [thread overview]
Message-ID: <s8ozf4vq44a.fsf@toolbox> (raw)
In-Reply-To: <DGO2XH72FZVX.WJ6DLQEY28YM@proxmox.com> (Shannon Sterz's message of "Wed, 25 Feb 2026 14:33:09 +0100")
"Shannon Sterz" <s.sterz@proxmox.com> writes:
> On Tue Feb 24, 2026 at 11:54 AM CET, Maximiliano Sandoval wrote:
>> We rephrase the current section putting more emphasis on the current
>> +Before {pve} 8.1, the ARC usage limit was set to '50 %' without clamping it to a
>> [..]
>> +maximum size. 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.
>
> this and the other patch in this series looks good to me, one small
> comment: maybe mention that this isn't something set by the installer or
> pve, but rather just the zfs default [1].
>
> [1]: https://openzfs.github.io/openzfs-docs/man/master/4/zfs.4.html#zfs_arc_max
>
> other than that, consider this:
>
> Reviewed-by: Shannon Sterz <s.sterz@proxmox.com>
>
>>
>> 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
Superseded-by: https://lore.proxmox.com/all/20260226084639.107816-1-m.sandoval@proxmox.com/
--
Maximiliano
next prev parent reply other threads:[~2026-02-26 8:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 10:54 [PATCH docs 0/2] " Maximiliano Sandoval
2026-02-24 10:54 ` [PATCH docs 1/2] " Maximiliano Sandoval
2026-02-25 13:33 ` Shannon Sterz
2026-02-26 8:51 ` Maximiliano Sandoval [this message]
2026-02-24 10:54 ` [PATCH docs 2/2] local-zfs: add reference to the zfs(4) manual Maximiliano Sandoval
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=s8ozf4vq44a.fsf@toolbox \
--to=m.sandoval@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.sterz@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