Conversation
This was referenced Aug 28, 2026
rcoh
force-pushed
the
codex/flamegraph-progress-events
branch
from
August 28, 2026 15:27
32870cb to
9362099
Compare
rcoh
force-pushed
the
codex/flamegraph-progress-events
branch
from
September 1, 2026 20:45
9362099 to
0c13510
Compare
jv1i
approved these changes
Sep 2, 2026
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
kind: "coverage"SSE events for every refinement update.kind: "partial"flamegraph trees at exponentially spaced file-coverage checkpoints.kind: "final"projection at 50,000 nodes.Why
The previous revision avoided the original 600 MB response by sending coverage-only events and building the tree once. That removed the payload explosion, but it also meant the UI had no renderable data until the expensive final projection completed, so users saw only a spinner while files folded.
Rebuilding the full exact tree after every file would restore the old CPU/allocation problem. Bounded, depth-limited previews provide useful incremental results without repeatedly constructing or serializing the final 50,000-node projection.
Protocol
flat-v1now streams:coverageafter each merge that does not cross a preview checkpoint.partialafter file coverage crosses 1, 2, 4, 8, 16, ... files.finalevent after the work list drains.The first cached seed batch contains one file so an existing folded set can produce a preview before the remaining cached files are merged in normal bounded batches.
Dependency
Depends on #848.
Stack
Validation
Validated on the complete stack:
cargo fmt --all -- --checkcargo clippy -p dial9-viewer --all-targets --all-features -- -D warningscargo nextest run -p dial9-viewer(530 passed)cargo nextest run -p dial9-viewer --stress-duration 20s(one full iteration, 530 passed)