-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
perf: improve knowledge base retrieval quality #9455
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
lxfight
wants to merge
2
commits into
AstrBotDevs:master
Choose a base branch
from
lxfight:perf/kb-retrieval-quality
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+178
−43
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
issue (complexity): Consider extracting normalization and candidate-building helpers so
fusefocuses on orchestration rather than detailed score and dict management.You can keep all the new behavior but make
fusemuch easier to follow by extracting a couple of helpers and removing duplicated logic.1. Extract score normalization into a helper
The dense/sparse normalization loops are identical. Factor them out so
fuseonly expresses what is normalized, not how:Use it in
fuse:(You may want a tiny helper for resolving
kb_idcleanly instead of the inlineorchain.)2. Introduce a small internal structure to reduce parallel dicts
Right now
vec_doc_id_to_dense,chunk_id_to_sparse,dense_metadata,fusion_scores,rrf_scoresall key offidentifier. A minimal internal “candidate” object lets you collapse these parallel maps:Then, in
fuse, you can build candidates in one place:After that:
dense_groups/sparse_groupscan be built fromcandidates.values()instead of separate dicts.fusion_scoresandrrf_scorescan be stored directly on_Candidateor in small dicts keyed byidentifier.FusedResultno longer needs to look back into multiple maps; everything is on the candidate.This reduces the cognitive load of keeping many coordinated dictionaries in sync while preserving all current behavior.