On 30 Dec 2017 at 11:52, Thorsten Schöning wrote: > That's the main difference, the VM where I have the problems has 48 GB > of RAM and currently 10 assigned vCPUs, formerly 6. The VMs where this > is not happening have only 2 vCPUs and 6 or 8 GB of RAM, where only 2-4 > GB are in use by apps and else is cache. The problematic VM has ~10 GB > in use by apps and everything else for caches and buffers.
> The only thing that really jumps out is the number of context switches > in the host and how long this happens. On the working host those climb > from ~6'500 to 10-15'000 for very few seconds, while on the > "non-working" host those climb from ~5'000 to 50'000 for a much longer > period of time. While in all cases the VMs itself don't have many > context switches themselfs. Could it be that your are oversubscribing your vCPUs? I mean if you assign more vCPUs to your VMs than you physically have then I guess it's expected to see lots of context switches on the host, and that would not good of course. HTH, Pierre _______________________________________________ clamav-users mailing list clamav-users@lists.clamav.net http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/contact.html#ml
