perf: coalesce compose inspector refresh work - #709
Open
baron wants to merge 2 commits into
Open
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
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
Follow-up to #535 after a performance-focused audit.
Review notes
The audit also identified larger possible costs in full-content rereads for selected worktree files and periodic Git selection reconciliation. Those are intentionally deferred until measured; this PR keeps the change small and addresses only confirmed redundant invalidation/work.
A Fable 5 High design review caught an unsafe first attempt to coalesce in-flight refreshes: a failed or cancelled request could consume the only completion event. That optimization was removed, preserving retry semantics while retaining safe completed-snapshot coalescing.
Validation
The PR-ready full root suite completed with four failures in unrelated concurrency/timing tests:
The changed coordinator suite remained green. A focused rerun was queued but cancelled before acquiring the machine-wide heavy slot because another worktree held it; hosted exact-head CI should provide the final broad signal.