From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Fiona Ebner <f.ebner@proxmox.com>
Subject: [pve-devel] applied: [PATCH proxmox-resource-scheduling] pve static: add one to avoid boosting tiny relative differences
Date: Wed, 22 Mar 2023 09:32:27 +0100 [thread overview]
Message-ID: <eec0c1a6-721f-cfa6-134c-9d0bf2e6ba37@proxmox.com> (raw)
In-Reply-To: <20230321164452.268358-1-f.ebner@proxmox.com>
Am 21/03/2023 um 17:44 schrieb Fiona Ebner:
> Only the relative difference for values between different alternatives
> is relevant, meaning 0.002 vs 0.004 and 0.2 vs 0.4 will influence the
> scoring in the same way. This is not really desirable, because values
> closer to 1.0 indicate higher load and thus should influence the
> scoring more than differences that are actually tiny, but big when
> viewed as a relative difference.
>
> To avoid the issue, simply add 1.0 to all values. Like that, 1.002 vs
> 1.004 will also be small when viewed as a relative difference.
>
> Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
> ---
> src/pve_static.rs | 10 ++++++----
> 1 file changed, 6 insertions(+), 4 deletions(-)
>
>
applied series (yesterday already), thanks!
next prev parent reply other threads:[~2023-03-22 8:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 16:44 [pve-devel] " Fiona Ebner
2023-03-21 16:44 ` [pve-devel] [PATCH proxmox-perl-rs 1/2] pve: test: resource scheduling: add test where memory is secondary to CPU Fiona Ebner
2023-03-21 16:44 ` [pve-devel] [PATCH proxmox-perl-rs 2/2] pve: test: resource scheduling: add another " Fiona Ebner
2023-03-22 8:32 ` Thomas Lamprecht [this message]
2023-10-05 9:50 ` [pve-devel] applied: [PATCH proxmox-resource-scheduling] pve static: add one to avoid boosting tiny relative differences Fiona Ebner
2023-11-06 17:21 ` [pve-devel] applied: " Thomas Lamprecht
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=eec0c1a6-721f-cfa6-134c-9d0bf2e6ba37@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=f.ebner@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