Repository navigation
docs: correct round 168's shared-cause guess for the other slow bench pages - #269
Merged
Merged
Conversation
… pages Checked foundation.zurb.com (24.8s in the 500-page run, untouched by this round's live testing) directly rather than assume the font-face fix (round 168, PR #267) also explains it: still ~40s after that fix, but DisableJS=true drops it to ~6.2s on the same page -- its slowness is JS-settle-related, not the font-face-slot bug round 168 fixed. cs.cmu.edu itself could not be cleanly re-measured: a careful single re-check well after the fix merged still showed ~45s, consistent with this round's own earlier live testing having triggered the origin's own throttling (escalating response times observed before the fix even shipped), which outlasted the session rather than the fix being ineffective -- the deterministic local test (already in PR #267) remains the real evidence for it. 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(24.8s in the 500-page run, untouched by this round's live testing) directly rather than assume the font-face fix (round 168, PR engine: fetch a font-face slot's candidate rules concurrently, not one at a time #267) also explains it: still ~40s after that fix, butDisableJS=truedrops it to ~6.2s on the same page — its slowness is JS-settle-related, not the font-face-slot bug round 168 fixed.cs.cmu.eduitself could not be cleanly re-measured: a careful single re-check well after the fix merged still showed ~45s, consistent with this round's own earlier live testing having triggered the origin's own throttling, which outlasted the session rather than the fix being ineffective — the deterministic local test (already in PR engine: fetch a font-face slot's candidate rules concurrently, not one at a time #267) remains the real evidence for it.Test plan
🤖 Generated with Claude Code