docs: Add per-second usage billing enhancement and design - #223
Open
JoseSzycho wants to merge 1 commit into
Open
docs: Add per-second usage billing enhancement and design#223JoseSzycho wants to merge 1 commit into
JoseSzycho wants to merge 1 commit into
Conversation
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.
Context
Compute currently doesn't record how much compute each project actually uses, which makes fair, consumption-based billing impossible. This PR adds the design work that defines how we'll meter per-second CPU and memory usage and hand it to the platform's billing pipeline.
What's included
docs/enhancements/per-second-usage-billing/README.md) that lays out the problem, our goals and non-goals, how running time becomes billable usage, how we stay accurate through failures, the alternatives we considered, and the standard production-readiness review questionnaire. It makes the billing model explicit: customers are billed per second, only while an instance is running.architecture-context.pumland a rendered PNG) showing how a customer's usage flows from Compute to the billing pipeline.issues/README.md) splitting the effort into a design issue and a build issue, ready to copy into the tracker.