services.concurrency for free tier

[jake]

@jerome

• user connections are indeed persistent, but not connections from us to your app

If you want “requests” concurrency, you can set type = "requests" in the [services.concurrency] block. By default we do connections concurrency which best fits a world of TCP services or websockets.

Hi @jerome, thanks for the reply! If connections from the fly load balancer to our app is not persistent, and my app is just doing simple HTTP REST handling, won’t the type = "request" have the same behaviour?

@jerome

Again, autoscaling is imperfect, but it’s correct that Fly will only consider scaling your app if it has > soft limit connections for some duration (a few seconds).

Is the measurement done at the app, or is it done at the load balance? E.g. 20 simultaneous connections from the load balancer to the app causes a scale, or 20 simultaneous connections to the load balancer?

Thanks!