Repository navigation
chore(infra): keep the dev host on Lightsail micro - #602
Merged
Merged
Conversation
On nano the dev runtime's 1 s polling sits at the 5% CPU baseline, burst credit stays at 0% and the post-merge deploy failed its health check, so dev was restored from its micro snapshot. Release stays nano while idle.
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
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.
Follow-up to #601. On
nano_3_0, dev's 1 s cycle and worker polling kept CPU at nano's 5% baseline and burst credit at 0%. The post-merge deploy (run 43626174198) then failed its health check and rolled back to the previous build on its own. On 15 Nov 2026 dev was restored tomicro_3_0from snapshotrewind-demo-micro-20261115, with the same static IP and CloudFront URL (returns 200). Release is idle and stays onnano_3_0; its comment now says to move it to micro before it runs the app.