perf(search): skip fuzzy correction on stopwords and cache cleanup statements#272
Merged
mksglu merged 1 commit intomksglu:mainfrom Apr 14, 2026
Conversation
…atements Two perf improvements in store.ts: 1. searchWithFallback fuzzy correction now skips stopwords — each fuzzyCorrect call queries the vocab DB + runs levenshtein, wasted on words like "update"/"test"/"fix" that get filtered from search anyway. 2. cleanupStaleSources now uses cached prepared statements instead of recompiling 3 SQL statements on every call, matching the pattern used by all other methods in ContentStore.
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
2 participants
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
searchWithFallbackwas runningfuzzyCorrect()on every word including stopwords likeupdate,test,fix. Each call queries the vocab DB + runs levenshtein comparisons, wasted on words that get filtered from the FTS5 query anyway.cleanupStaleSources()was the only method creating 3 new prepared statements per call. All other methods in ContentStore cache theirs in the constructor. Now consistent.Test plan
cleanupStaleSourcesworks correctly with cached statementscleanupStaleSourcescan be called multiple times (reuse)