From: "DERUMIER, Alexandre" <Alexandre.DERUMIER@groupe-cyllene.com>
To: "pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>
Subject: [pve-devel] auto ballooning && ksm thresholds both at 80%
Date: Thu, 30 Dec 2021 10:47:12 +0000 [thread overview]
Message-ID: <ee3aacec76017c117f04614494cfb79fdbc740d6.camel@groupe-cyllene.com> (raw)
Hi,
I'm still working on ha manager ressource aware && loadbalancing (I
have some big improvements to send soon before review)
I currently looking at memory balancing doing a lot of tests,
and I wonder if auto-ballooning threshold shouldn't be a little bit
bigger than ksm.
Currently both are at 80%,
that mean that ballooning is vm reducing memory fast, and ksm don't
have time to run.
as ballooning is a lot more intrusive than ksm, I wonder if it couldn't
be set to something like 90%.
Like this, ksm can try to keep memory at 80%, and if memory is growing
too fast up to 90% or if ksm can't really deduplicate pages anymore, we
have ballooning in action.
What do you think about it ?
next reply other threads:[~2021-12-30 10:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-30 10:47 DERUMIER, Alexandre [this message]
2021-12-31 14:31 Dietmar Maurer
2022-01-03 8:20 ` DERUMIER, Alexandre
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=ee3aacec76017c117f04614494cfb79fdbc740d6.camel@groupe-cyllene.com \
--to=alexandre.derumier@groupe-cyllene.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