chore(bench): fixtures + analysis/transport benchmarks + baseline - #25
Merged
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.
Slice 2.5 foundation: measure before optimizing (the ADR-010 principle).
Key baseline finding: the OCaml analysis is sub-millisecond on the large fixture (didChange->diagnostics 1.9ms p95). The one hot spot is semanticTokens/full on large at ~70ms p95 -- encoding/transport bound (of_blocks itself is 0.83ms), exactly what semantic tokens delta targets. The planned LSP memo/cache optimization would tune work already 100x under budget; the data redirects effort to semantic tokens delta and the frontend full-doc scanners (measured separately in httui-desktop).