From: Roland via pve-user <pve-user@lists.proxmox.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Cc: Roland <devzero@web.de>
Subject: Re: [PVE-User] A less aggressive OOM?
Date: Thu, 10 Jul 2025 18:11:41 +0200 [thread overview]
Message-ID: <mailman.1280.1752163947.395.pve-user@lists.proxmox.com> (raw)
In-Reply-To: <mailman.1274.1752159599.395.pve-user@lists.proxmox.com>
[-- Attachment #1: Type: message/rfc822, Size: 10695 bytes --]
From: Roland <devzero@web.de>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] A less aggressive OOM?
Date: Thu, 10 Jul 2025 18:11:41 +0200
Message-ID: <98ace9cf-a47f-40cd-8796-6bec3558ebb0@web.de>
imho, killing processes because of arc using too much ram which can't be
reclaimed fast enough is a failure in overall memory coordination.
we can set zfs limits as a workaround, yes - but zfs and oomkiller is to
blame !!!
1. zfs should free up memory faster, as memory is also freed from
buffers/caches
2. oomkiller should put pressure on arc or try reclaim pages from that
first, instead of killing kvm processes. maybe oomkiller could be made
arc-aware!?
roland
>On 7/10/2025 11:08 AM, Roland via pve-user wrote:
>if OOM kicks in because half of the ram is being used for
caches/buffers, i would blame OOMkiller or ZFS for tha. The problem
should be resolved at zfs or memory management level.
>Absolutely no!
>You are responsible for giving ZFS the limits. As even described in
the proxmox documentation here:
>https://pve.proxmox.com/wiki/ZFS_on_Linux#sysadmin_zfs_limit_memory_usage
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
Am 10.07.25 um 16:49 schrieb dorsy via pve-user:
> On 7/10/2025 11:08 AM, Roland via pve-user wrote:
> if OOM kicks in because half of the ram is being used for
> caches/buffers, i would blame OOMkiller or ZFS for tha. The problem
> should be resolved at zfs or memory management level.
>
> Absolutely no!
> You are responsible for giving ZFS the limits. As even described in
> the proxmox documentation here:
> https://pve.proxmox.com/wiki/ZFS_on_Linux#sysadmin_zfs_limit_memory_usage
>
>> _______________________________________________
>> pve-user mailing list
>> pve-user@lists.proxmox.com
>> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
>
>
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
[-- Attachment #2: Type: text/plain, Size: 157 bytes --]
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
next prev parent reply other threads:[~2025-07-10 16:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-07 9:26 Marco Gaiarin
2025-07-07 21:39 ` Victor Rodriguez
2025-07-08 16:31 ` Marco Gaiarin
2025-07-10 8:56 ` Victor Rodriguez
2025-07-10 9:08 ` Roland via pve-user
2025-07-10 14:49 ` dorsy via pve-user
2025-07-10 16:11 ` Roland via pve-user [this message]
[not found] ` <98ace9cf-a47f-40cd-8796-6bec3558ebb0@web.de>
2025-07-10 16:15 ` dorsy via pve-user
2025-07-13 14:28 ` Marco Gaiarin
2025-07-08 12:05 ` Roland via pve-user
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.1280.1752163947.395.pve-user@lists.proxmox.com \
--to=pve-user@lists.proxmox.com \
--cc=devzero@web.de \
/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