1

When I deploy a custom managed VM module, it always starts out with the max number of instances before it scales down.

Why does this happen and is there a way around this?

I suspect it is because cpu utilization is higher than the target during startup. But shouldn't the scaler know to not evaluate utilization during startup?

My scaling settings are as follows:

automatic_scaling:
  min_num_instances: 2
  max_num_instances: 20
  cool_down_period_sec: 60
  cpu_utilization:
    target_utilization: 0.5
user2771609
  • 1,867
  • 1
  • 15
  • 36

1 Answers1

1

coolDownPeriodSec sets how long the autoscaler waits after the VM starts to use data from that VM. The autoscaler 60 second default is probably too low. Try setting it to 120 to give it more time.

Mathew Ryden
  • 26
  • 2