Document one-app-per-user scale limit for autostop#2399
Open
Document one-app-per-user scale limit for autostop#2399
Conversation
Add a footgun to the per-user dev environments blueprint explaining that the Fly Proxy autostop loop can't keep idle Machines stopped at thousands-of-Machines scale, with pointers in the autostop config and proxy reference docs back to the dynamic-routing pattern.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary of changes
Add a footgun to the per-user dev environments blueprint covering what happens when you put thousands of user Machines into a single app: the Fly Proxy's autostop loop is rate-limited (one Machine per region per pass, every few minutes) and can't keep up at that scale, so most idle Machines stay running. Also notes the shared-secrets / flat-network consequence and points readers to stop-when-idle as the alternative.
Cross-links from the autostop config guide and the Fly Proxy autostop reference back to the dynamic-routing pattern, so readers landing on the autostop docs while running this shape are pointed to a workable approach.
Notes
Came out of a support thread where a customer running thousands of Machines in one app discovered the rate-limited stop loop the hard way. The behavior is already documented in the proxy reference; this just makes the implication explicit at the per-user-dev page and adds the reverse pointers.