From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [45.144.208.40]) by lore.proxmox.com (Postfix) with ESMTPS id 02EBA1FF0B6 for ; Thu, 12 Nov 2026 17:36:53 +0100 (CET) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 6154121679; Thu, 12 Nov 2026 17:36:51 +0100 (CET) Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Date: Thu, 12 Nov 2026 17:36:45 +0100 Message-Id: From: "Daniel Kral" To: "Daniel Kral" , Subject: superseded: [PATCH-SERIES ha-manager 00/16] some sid parsing and LRM speedup improvements X-Mailer: aerc 0.22.0-10-g6373ac9d2179-dirty References: <20260720123705.216089-1-d.kral@proxmox.com> In-Reply-To: <20260720123705.216089-1-d.kral@proxmox.com> X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1794501405922 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.583 Adjusted score from AWL reputation of From: address DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment (newer systems) RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: LGTBNAF577XV5LYNIM23QVGC2ROC3O6M X-Message-ID-Hash: LGTBNAF577XV5LYNIM23QVGC2ROC3O6M X-MailFrom: d.kral@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Superseded-by: https://lore.proxmox.com/pve-devel/20261112163113.294302-3-d= .kral@proxmox.com/ On Mon Jul 20, 2026 at 2:36 PM CEST, Daniel Kral wrote: > It was reported in the enterprise support, that nodes with high counts > of HA resources (250+ HA resources) cause the pve-ha-lrm daemon to > consumes quite a lot of CPU time while being idle. Furthermore, > migration commands for HA resources might take quite a long time to be > actually committed when the max_workers value is not high enough. > > [...]