[perk]

Does this mean I can spin up multiple instances of _the same_ application on the fly, each running on it's own VM?

For example, we have a queue that handles video encoding. I would like to have 0-N encoders running at the same time, based on demand.

Spin up time is important as well, since I typically provide test renders triggered from the UI.

[NamelessChic]

Fly can do this without the new Machines functionality, it's a big selling point for them.

You set a min and max number of VMs to run. Set the watermark for users per machine. And they automatically scale up and down depending on the number of connections. It will even figure out where in the world all the connections are coming from, and spin up the new VM in a region near to them.

So if your video encoding was requested via HTTP(S) connections then this would be trivial.

https://fly.io/docs/reference/scaling/#autoscaling

[lewisl9029]

Right, I was wondering about this too. There are mentions of instances vs machines, so I'm hoping it's possible to spin up multiple instances of the same machine to run tasks concurrently, but I haven't found this explicitly confirmed anywhere yet.

[perk]

Please reply here if you find out, I'll do the same :)