fix(search): bound query result caches - #20
Merged
damienriehl merged 1 commit intoAug 22, 2026
Merged
Conversation
damienriehl
marked this pull request as ready for review
August 21, 2026 19:58
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
Long-running consumers no longer retain results for every unique label, definition, and prefix query. Search behavior stays unchanged, while process-lifetime query caches retain at most 128 entries each.
A
folio-resolvesynthetic workload exposed the impact. After one passage,_basic_searchheld 1,707 entries and the case-insensitive prefix cache held 766 entries; process RSS reached 1.29 GiB. The same unbounded growth helped drive a 225-item run to a 30.48 GB peak.Validation