bhouse-nexthop commented on PR #14109: URL: https://github.com/apache/cloudstack/pull/14109#issuecomment-6341233672
> is this similar to #10997 ? No, this is vastly different. The primary difference I'd say is the fact that this looks at actual utilization numbers not just allocated numbers. With overprovisioning and the use of free page reporting you can have hosts with greatly varying utilization and this looks to even that out. Its got weighting knobs for each of the cpu and memory utilization vs allocation, with sane defaults. It also weights actual VM count as the agent can struggle with managing more smaller vms vs fewer larger vms so it helps balance those out as well. In our environment we run mostly things like developer VMs and ephemeral runners for CI/CD tasks so we need overprovisioning as the allocations for those VMs are way different then the actual utilization (4x memory overcommit and 10x cpu overcommit). With this balancing algorithm we went from daily OOM events and slow agent provisioning and destroy of VMs to zero of both events. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
