Autoscale doesn't seem to work with hard_limit = 1 and soft_limit = 1

8

Hi @viraj! There might be a few reasons for this:

  1. We just shipped (like today) a new autoscaler that is much more responsive. I opted your apps into it.
  2. Your apps are technically using connection concurrency. If you’re sending multiple requests over shared connections with k6s, it won’t affect the scaling numbers.

For #2, I would suggest adding type = "requests" to the concurrency block in your fly.toml.

Will you run your test again and see if those things improve? With new autoscaling you should see fly status show new instances within about 30s of a test starting.

1 Like