Repository navigation
docs: document SVG rasterisation cost as a Known gap (confirmed on two pages) - #272
Merged
Merged
Conversation
…o pages) Round 169's own follow-up CPU profiling of foundation.zurb.com (one of the slow pages from the 500-page bench run, confirmed round 168's font-face fix didn't apply here) pinned its ~30s render time to SVG rasterisation: 84% of CPU samples inside rasterx's Draw path, mostly per-pixel gradient-color sampling. DisableJS=true drops the SAME page to ~6.2s not because JS execution itself is CPU-slow, but because the no-JS render has less SVG content to rasterise than the JS-settled page actually ends up with. This independently confirms an earlier, never-written-down finding from investigating docs.docker.com's own slow render (a decorative dot-pattern.svg background, cost scaling with output area) -- the same architectural question, now with two real-world triggers instead of one. Not fixed: both live options (cap output resolution, budget rasterisation time) change rendering output, a decision this session has twice deferred rather than pick unilaterally. Also tightens round 168's own "JS-settle-related" phrasing for the same page now that the actual cause is pinned down precisely. Co-Authored-By: Claude Sonnet 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.
Summary
foundation.zurb.com(one of the slow pages from the 500-page bench run, confirmed round 168's font-face fix didn't apply here) pinned its ~30s render time to SVG rasterisation: 84% of CPU samples inside rasterx'sDrawpath, mostly per-pixel gradient-color sampling.DisableJS=truedrops the same page to ~6.2s not because JS execution itself is CPU-slow, but because the no-JS render has less SVG content to rasterise than the JS-settled page actually ends up with.docs.docker.com's own slow render (a decorativedot-pattern.svgbackground, cost scaling with output area) — the same architectural question, now with two real-world triggers instead of one.Test plan
🤖 Generated with Claude Code