Add memfree migration selector for flush #152

New Issue

joshuaboniface · 2022-05-18T03:39:56-04:00

joshuaboniface commented

2022-05-18 03:39:56 -04:00

Currently the mem selector based on allocated/provisioned memory is not sufficient to handle situations where some VMs are provisioned large but have low usage, and others are provisioned large but have high usage. This can cause situations where there is a massive discrepancy between the actual memory utilization on a node and the allocated/provisioned memory on the node. Thus, the migration selector can choose a suboptimal target for a VM migration that could result in swapping/low performance or worse (OOMs, etc.).

Add another option here for memfree which would instead choose the node with the "most free memory" instead. This can then be used on memory-constrained clusters where this difference could be significant.

Currently the `mem` selector based on allocated/provisioned memory is not sufficient to handle situations where some VMs are provisioned large but have low usage, and others are provisioned large but have high usage. This can cause situations where there is a massive discrepancy between the actual memory utilization on a node and the allocated/provisioned memory on the node. Thus, the migration selector can choose a suboptimal target for a VM migration that could result in swapping/low performance or worse (OOMs, etc.). Add another option here for `memfree` which would instead choose the node with the "most free memory" instead. This can then be used on memory-constrained clusters where this difference could be significant.

joshuaboniface added the

Daemon

improvement

labels 2022-05-18 03:39:56 -04:00

joshuaboniface referenced this issue from a commit

2022-05-18 03:47:42 -04:00

Add migration selector via free memory

joshuaboniface closed this issue

2022-05-18 03:47:42 -04:00

joshuaboniface referenced this issue from a commit

2023-09-01 15:58:46 -04:00

Add migration selector via free memory