Repository navigation
docs(known-issues): the 22.6s symbol call was contention, not code - #158
Merged
Merged
Conversation
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the
|
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.
Measured with the same probe on the pre-fix tree (25648b3) and on main: 1224 ms vs 1128 ms for the same qualified query; warm calls 40 ms; cold server start: initialize 3.4 s, health 2.7 s, first search 0.7 s, first get_symbol_info 284 ms. The 22.6 s observation came from concurrent load (a full suite was running in the same session). The same probe also confirms the fixes: no.such.symbol returned '1 defs, 15 callers' before and 'not found' after; callees for intent_recall were capped at 10 before and are 23 now.