Scale to zero — this service is idle by default - #1
Merged
Conversation
Self-hosted installs push on a 30-minute background tick, so this is
idle by design. Today, with no self-hosted installs, it serves nothing.
The comment justifying always-warm reached the opposite conclusion from
the same facts: that ticks "arrive on their own schedule, not in
response to user traffic" was treated as a reason to stay warm, when it
is exactly what makes the workload intermittent. It also asserted "no
real cost benefit at this service's expected traffic" — at 48 requests
a day per install the machine is idle ~95% of the time.
Verified rather than assumed:
- Boot is ~3s, inside Fly's ~8s proxy window for an auto-started
machine. (The Sentinel AI agent needs 10s, missed that window, and
had every wakeup fail until it was kept warm — this is the check
that matters.)
- A failed push is fail-soft and lossless: push_pending_changes never
raises, and cursors only advance on confirmed success, so a missed
cycle's data simply waits for the next tick. The operator's local
SQLite remains the source of truth throughout.
Co-Authored-By: Claude Opus 5 <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
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.
Self-hosted installs push on a 30-minute background tick. Today, with no self-hosted installs, it serves nothing.
The comment justifying always-warm reached the opposite conclusion from the same facts — that ticks "arrive on their own schedule, not in response to user traffic" was treated as a reason to stay warm, when it's exactly what makes the workload intermittent. It also claimed "no real cost benefit at this service's expected traffic"; at 48 requests/day per install the machine is idle ~95% of the time.
Verified, not assumed:
RemoteDisconnecteduntil it was kept warm.push_pending_changesnever raises, and cursors only advance on confirmed success — a missed cycle's data waits for the next tick. The operator's local SQLite stays the source of truth throughout.🤖 Generated with Claude Code