Autosuspend doesn't work with multiregion scaling?

Questions / Help
,
1

We have been using autosuspend since beta, and it was among our favorite Fly.io feature since! The ability to add redudancy without incurring significant performance/cost penalty is huge!

Everything works as promised with very little fiddling scaling to a single region:

fly scale count 2 --region sjc

image
image1148×933 161 KB

The secondary spins down and only comes online during traffic spikes.

We encountered an sjc outage recently, so I’m experimenting with multi-region scaling:

fly scale count 5 --region sjc,lax

However, autosuspend seem to no longer work as well, with the machines up almost all the time, despite similar traffic levels:

image
image1141×929 239 KB

Have I mistaken how multiregion works, or perhaps a misconfig fly.toml?

2

Might not be auto-suspend. You can switch back to auto-stop and see if this issue persists?

Our multi-region app, which to be fair gets a LOT of traffic (est. 300 to 500 reqs/s), has faced the issue of machines spinning up (apparently needlessly) then never spinning down, for quite a while now: Overriding staged secrets for Machines - #7 by ignoramous

If you’re on the Launch plan (or higher), consider writing to Fly’s support. They’re pretty responsive.

3

I’ll give support a shot and see if they can identify anything for us.

Will report back!

1 Like
4

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.