Hi Sven,
the reason is that the rule is a bit more complex now. KSM is started when free
memory drops below 20% or if the ksm_shareable value gets above 80% of
available memory.
the relevant rule in the policy is:
(defvar ksm_pressure_threshold (* Host.mem_available ksm_free_percent))
(defvar
Hi,
any update why this may have happened?
Am 04.11.2013 21:02, schrieb Itamar Heim:
I'm more concerned by the fact ksm consumed RAM supposedly before memory
usage was 80%.--
Mit freundlichen Grüßen / Regards
Sven Kieske
Systemadministrator
Mittwald CM Service GmbH Co. KG
Königsberger
Hi Frank,
we do not currently have anything in the engine that would allow you to do
this. If you create an oVirt RFE bug for it it would make it easier for us to
add the feature and track the progress.
However you can update the policy file you found to accomplish this. Just set
(defvar
Hi Martin,
On 2013-11-04 11:12, Martin Sivak wrote:
we do not currently have anything in the engine that would allow you
to do this. If you create an oVirt RFE bug for it it would make it
easier for us to add the feature and track the progress.
good advice, here we go:
On 11/04/2013 01:24 PM, Frank Wall wrote:
Hi Martin,
On 2013-11-04 11:12, Martin Sivak wrote:
we do not currently have anything in the engine that would allow you
to do this. If you create an oVirt RFE bug for it it would make it
easier for us to add the feature and track the progress.
good
Hi,
recently I've noticed that ksmd is using quite a lot CPU on
my oVirt node. While I have plenty RAM, my CPU is way slow.
Thus ksmd is eating up the most limited ressource here.
Is it supported to use custom settings for ksmd? I've noticed
that it is handled by MoM:
6 matches
Mail list logo
