Hello and thank you very much for your reply.

I'm terribly sorry for being so late to respond. 

I thought the same, that dropping the cache was more of a workaround and not a 
real solution but truthfully I was stuck and can't think of anything more than 
how much I need to upgrade the memory on the nodes. I try to find info about 
other ovirt virtualization set-ups and the amount of memory allocated so I can 
get an idea of what my set-up needs. The only thing that I found was that one 
admin had set ovirt up with 128GB and still needed more because of the growing 
needs of the system and its users and was about to upgrade its memory too. I'm 
just worried that ovirt is very memory consuming and no matter how much I will 
"feed" it, it will still ask for more. Also, I'm worried that there one, two or 
even more tweaks in the configurations that I still miss and they'd be able to 
solve the memory problem. 

Anyway, KSM is enabled. Sar shows that the committed memory when a Windows 10 
VM is active too (alongside Hosted Engine of course, and two Linux VMs - 1 
CentOS, 1 Debian) is around 89% in the specific host that it runs (together 
with the Debian VM) and has reached up to 98%.

You are correct about the monitoring system too. I have set up a PRTG 
environment and there's Nagios running but they can't yet see ovirt. I will set 
them up correctly the next few days.

I haven't made any changes to my tuned profile. it's the default from ovirt. 
Specifically, the active profile says it's set to virtual-host.

Again I'm very sorry for taking me so long to reply and thank you very much for 
your response. 

Best Regards,
Maria Souvalioti
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/G4YELWF5L4AKUT3OH4C4QJHHEEJPCI3G/

Reply via email to