Repository navigation
docs: the hosted deployment's bounds moved, so say the current ones - #15
Merged
Merged
Conversation
The service was on the free plan when this section was written: ten milliseconds of CPU per request, which produced a fitted table of per-renderer PNG ceilings between 48 and 112, and no PNG at all for flowfield. It is on the paid plan now, thirty seconds, and the table has been replaced by one bound per format. Also says that drawing a new mark is rate limited while fetching an existing one is not, because that is the difference a caller can actually run into. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SU6ycrqMbQ8AVxzxYgdC5C
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.
Follow-up to #14, which described the service as it was on the Workers free plan.
That plan allowed ten milliseconds of CPU per request, and exceeding it did not degrade gracefully — the request was killed and nothing was cached, so a URL stayed broken rather than being slow once. It produced a fitted table of per-renderer PNG ceilings between 48 and 112, and no PNG at all for
flowfield, whose particle simulation costs the same at sixteen pixels as at five hundred.The deployment is on the paid plan now: thirty seconds. The worst case it can be asked for measures a p99 near nineteen milliseconds, so the fitted table has been replaced by one bound per format — 1024 for SVG, 128 for PNG — and every renderer is served in both.
Also adds a sentence on rate limiting, because that is the difference a caller can actually run into: fetching a mark that already exists is not limited, drawing a new one is, per address.
🤖 Generated with Claude Code
https://claude.ai/code/session_01SU6ycrqMbQ8AVxzxYgdC5C