From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 2A39188B9 for ; Wed, 16 Nov 2022 10:18:37 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 06EC41CA05 for ; Wed, 16 Nov 2022 10:18:37 +0100 (CET) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS for ; Wed, 16 Nov 2022 10:18:36 +0100 (CET) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 40453448D6 for ; Wed, 16 Nov 2022 10:18:36 +0100 (CET) Message-ID: <88f4eabe-83f4-acbc-4cde-240c16d54883@proxmox.com> Date: Wed, 16 Nov 2022 10:18:35 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:107.0) Gecko/20100101 Thunderbird/107.0 From: Thomas Lamprecht To: Proxmox VE development discussion , Fiona Ebner References: <20221110143800.98047-1-f.ebner@proxmox.com> <20221110143800.98047-3-f.ebner@proxmox.com> Content-Language: en-GB In-Reply-To: <20221110143800.98047-3-f.ebner@proxmox.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-SPAM-LEVEL: Spam detection results: =?UTF-8?Q?0=0A=09?=AWL -0.031 Adjusted score from AWL reputation of From: =?UTF-8?Q?address=0A=09?=BAYES_00 -1.9 Bayes spam probability is 0 to 1% KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict =?UTF-8?Q?Alignment=0A=09?=NICE_REPLY_A -0.001 Looks like a legit reply (A) SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF =?UTF-8?Q?Record=0A=09?=SPF_PASS -0.001 SPF: sender matches SPF record Subject: Re: [pve-devel] [PATCH proxmox-resource-scheduling 2/3] add pve_static module X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Nov 2022 09:18:37 -0000 Am 10/11/2022 um 15:37 schrieb Fiona Ebner: > Models usage of guests and nodes, and allows scoring nodes on which to > start a new service via TOPSIS. For this scoring, each node in turn is > considered as if the service was already running on it. > > CPU and memory usage are used as criteria, with memory being weighted > much more, because it's a truly limited resource. For both, CPU and > memory, highest usage among nodes (weighted more, as ideally no node > should be overcommited) and average usage of all nodes (to still be overcommitted > able to distinguish in case there already is a more highly commited committed > node) are considered. something like this would be also great to have in the docs, as it gives some relatively high level (thus user digestible) insight.