AMP

AMP copied to clipboard

Dev Note: WHMCS deployments currently don't check memory usage and can result in over-provisioning.

This might be to do with how the provision score is calculated in ProvisionFitness.Score

Yeah, there was some discussion in the enterprise channel about this. It looks like the score is skewed by the values. I was thinking we could make it configurable so people can pick to base it on instance count, memory, or CPU instead of assuming.

A note on this is that the provisioning would likely be better off looking at the current restrict settings for all systems, for instances where, for example, you might have an empty node and another node with 4 12GB palworld servers on it - if it just looked at current usage, it would weigh the two options the same - whereas it should factor in what's actually being used as well as what is provisioned for use (likely as a divisible of the total RAM within the system)