perf(interrupt-rotation): parallelize slow sections with fragments - #74
Merged
sfc-gh-bnisco merged 2 commits intoJul 27, 2026
Merged
Conversation
Previously the page fetched the full open issue/PR snapshot synchronously at the top of the script and fetched the monitored-repo PRs inline mid-page, so both blocked the main thread in series before the existing parallel fragments were even dispatched. The heavy CI-artifact downloads never overlapped with the issue/PR fetch. Move every slow data source into a parallel=True fragment and reduce the main body to fast chrome (title, sidebar, header, dividers). The scattered action items are grouped into two fragments that share the cached issue/PR builder, so the snapshot is still fetched once but now overlaps with the CI metrics, flaky tests, monitored-repo PRs, reported bugs, and repro checks. Wall-clock drops from the sum of the blocking fetches to roughly the slowest single one. Visual order, help text, and column configs are unchanged. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The two action-item fragment docstrings claimed the snapshot was "grouped into a single parallel fragment so it is fetched once", but the snapshot is actually read from two separate fragments. Clarify that the fetch-once guarantee comes from st.cache_data memoization, and document why the split into two fragments exists: it preserves the original page order (issue tables at the top, PR tables at the bottom, independent-source sections in between) so a future reader does not collapse it and reorder the page. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
sfc-gh-bnisco
marked this pull request as ready for review
July 27, 2026 17:51
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.
Previously the page fetched the full open issue/PR snapshot synchronously at the top of the script and fetched the monitored-repo PRs inline mid-page, so both blocked the main thread in series before the existing parallel fragments were even dispatched. The heavy CI-artifact downloads never overlapped with the issue/PR fetch.
Move every slow data source into a parallel=True fragment and reduce the main body to fast chrome (title, sidebar, header, dividers). The scattered action items are grouped into two fragments that share the cached issue/PR builder, so the snapshot is still fetched once but now overlaps with the CI metrics, flaky tests, monitored-repo PRs, reported bugs, and repro checks. Wall-clock drops from the sum of the blocking fetches to roughly the slowest single one.
Visual order, help text, and column configs are unchanged.