Repository navigation
Conversation
…cloud streams when away, and start Neon at its smallest size - A wake lands where it was asked for (the next whole second), not at a random point inside a grid as wide as the wait. - Nothing is looked at "just in case": a loop with nothing left sleeps until a write wakes it (role_loop_due.due_ms may be empty), a sweep runs on the role's next pass once its interval passed, and only a look a loop asked for books a wake. - A serverless writer runs its loops' safety looks only while it has work, listens to the database only while busy (a connection lost while quiet stays down until work arrives), and rings every role only after a real loss. - Background work that outlives a request (a lifecycle command, a run's delivery, a program's infra start) and a broker line keep the process listening until they end. - A build announces itself when it starts; the Cloud Build Pub/Sub push that woke the dispatcher for every build in the project is gone. - The VS Code extension closes its live streams to a remote install after 5 minutes away and reopens them on return. - Tangle's database skill creates Neon at 0.25 to 1 CU, asleep after 5 minutes, and the cost notes match. - The per-instance terminate warning names the instance's infra plainly. - MEMORY: keep the hot path fast and the install able to scale to zero.
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.
An idle GCP install never scaled to zero and kept Neon awake. Causes and fixes:
role_loop_due.due_msmay be empty, one released migration); sweeps no write wakes run on the role's next pass once their interval passed; only a look a loop asked for books a wake.Listening::WhileBusy, aBusyguard held by every request to the end of its body, a broker line, and work that outlives its request). A connection Neon closes while the process is quiet stays down until work arrives, and that reconnect does not ring every role.Checked locally: nextest (3387), doc tests, clippy, parse-only build, examples, db tests (740), JS packages, extension compile, docs, terraform validate, and four e2e tests (a run, an infra stop and cancel, a drain, a program starting instance infra). The behaviour on a real GCP install is not tested here.