Publish Cloud Dev capacity benchmark - #121
Merged
Merged
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
2 participants
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.
Publishes the human-readable Cloud Dev capacity result on the canonical Cloud managed-runtime guide.\n\nThe page now states the exact provisioned 1-vCPU/1-GB plan shape, defines the fixed Standard Workflow comparison, reports completion and scheduling latency, and gives 30-day workflow and workflow-plus-activity equivalents. It also makes clear that this is a measured Dev baseline rather than an SLA or semantic-operation billing model.\n\nThe result uses the same isolated single-host topology and resource limits used by Cloud Dev provisioning. No separate Cloud benchmarks route is introduced.