Correct me if I’m wrong, but AFAIK autoscaling in Fly only works based on concurrent connections.
Is CPU usage also taken into account?
Eg:
I’m working on a service for encoding audio files with ffmpeg which is pretty heavy CPU intensive. Ideally I’d want a new VM to spin up if the current VM is already encoding a file.
Hooking up to a Fly-hosted prometheus metric would be great! This is how I have achieved scaling based on a Buildkite queue depth using the Kubernetes HPA, with much pain involved
We don’t scale fast enough to do that effectively. Right now, scaling happens as a background process that uses metrics to pick the count. Metrics are only scraped every 15s, so there’s some lag before we even start a VM.