Repository navigation
perf(containers): 15m of idle, not an hour and not two - #48
Merged
Merged
Conversation
Memory and disk bill on what is provisioned, for every awake second, so with the uptime monitor undeployed this timeout is the only thing bounding what an idle container costs. All three drop to 15m. demo 1h -> 15m enterprise 1h -> 15m demo-tasks 2h -> 15m demo-tasks had the longest tail and the least reason for it. The 2h predates the teardown and carries no stated rationale; the board is ephemeral by design, demo jobs run for seconds, and the gateway forwards every tasks call — so the upstream stays awake exactly as long as anyone is actually using it, and there is no state here worth paying to keep warm. A poll that does land on a cold start gets the 503-and-retry the Worker already returns. The cost is a ~1.7s cold start for the first visitor after a quiet quarter hour, measured on lite in #46. That is a fair trade for a demo people arrive at one at a time rather than in a steady stream, and the enterprise gateway has more reason still: it sits behind a sign-in, so it is idle more of the time than the demo is. Verified after deploy: all three healthy, tools/list returns 8 tools across three namespaces with no partialFailure, and jobs__start_job still mints through the affinity pin. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
The last piece of the container bill. Memory and disk bill on what is provisioned, for every awake second — and with
fold-uptimeundeployed,sleepAfteris the only thing bounding how long an idle container keeps costing money.fold-demo1h15mfold-enterprise1h15mfold-demo-tasks2h15mdemo-tasks had the longest tail and the least reason for it
The
2hpredates the teardown and carries no stated rationale. It is safe to cut:tasks/*call, so the upstream stays awake exactly as long as anyone is actually using it503 demo-tasks is starting, retry in a few secondsfrom the WorkerWhat it costs
A ~1.7s cold start for the first visitor after a quiet quarter hour — measured on
litein #46. Fair for a demo people arrive at one at a time rather than in a steady stream. The enterprise gateway has more reason still: it is behind a sign-in, so it idles more of the time than the demo does.Verified after deploy
demo,enterprise,tasks/healthall 200tools/listreturns 8 tools acrosscfdocs(2),git(5),jobs(1), norun.fold/partialFailurejobs__start_jobstill mints through the affinity pin (demo-job-8,run.fold/upstream: demo-tasks)All three are deployed.
🤖 Generated with Claude Code