public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Dominik Rusovac <d.rusovac@proxmox.com>, pve-devel@lists.proxmox.com
Subject: applied: [PATCH pve-ha-manager 2/2] fix #7974: env: pve2: set dynamic service mem value to host memory usage
Date: Tue, 22 Sep 2026 22:04:23 +0200	[thread overview]
Message-ID: <11d5cb89-81b0-445c-b470-9cd68d5a6f5a@proxmox.com> (raw)
In-Reply-To: <20260828123239.1110595-2-d.rusovac@proxmox.com>

Am 28.08.26 um 14:32 schrieb Dominik Rusovac:
> Make memory accounting in dynamic CRS consistent.
> 
> Atm the imbalance value that triggers rebalancing is derived from the
> guests' host memory usage, which corresponds to the respective host-side
> cgroup footprints of the guests. However, the scheduler's decision
> procedure predicts the changes in imbalance caused by migration
> candidates based on memory usage (inside the guests). This discrepancy
> can lead to oscillating migrations, as described in detail in [0].
> 
> For VMs, host memory usage is the relevant stat, as it better describes
> the actual cost of running on a node than memory usage. Host memory
> usage is not available for containers, so fall back to memory usage for
> containers.
> 
> [0] https://bugzilla.proxmox.com/show_bug.cgi?id=7974
> 
> Signed-off-by: Dominik Rusovac <d.rusovac@proxmox.com>
> ---
>  src/PVE/HA/Env/PVE2.pm | 6 +++++-
>  1 file changed, 5 insertions(+), 1 deletion(-)
> 
>

applied, thanks!




      parent reply	other threads:[~2026-09-22 20:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-28 12:32 [PATCH pve-ha-manager 1/2] fix #7974: run make tidy Dominik Rusovac
2026-08-28 12:32 ` [PATCH pve-ha-manager 2/2] fix #7974: env: pve2: set dynamic service mem value to host memory usage Dominik Rusovac
2026-09-20 15:24   ` Michael Ryom
2026-09-22 20:04   ` Thomas Lamprecht [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=11d5cb89-81b0-445c-b470-9cd68d5a6f5a@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=d.rusovac@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal