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 ksm_committed Host.ksm_shareable)
(if (and (> (+ ksm_pressure_threshold ksm_committed) Host.mem_available)
(< (Host.StatAvg "mem_free") ksm_pressure_threshold))
Regards
--
Martin Sivák
msi...@redhat.com
Red Hat Czech
RHEV-M SLA / Brno, CZ
----- Original Message -----
> 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 Straße 6
> 32339 Espelkamp
> T: +49-5772-293-100
> F: +49-5772-293-333
> https://www.mittwald.de
> Geschäftsführer: Robert Meyer
> St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen
> Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen
> _______________________________________________
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
