-
Notifications
You must be signed in to change notification settings - Fork 12
fix(perf): apply cachedStmt to buildTestFileIds static SQL #575
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
Merged
Merged
Changes from all commits
Commits
Show all changes
3 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.
buildTestFileIdsis a private helper called exclusively fromstatsData, which opens a fresh DB instance viaopenReadonlyOrFail(customDbPath)and closes it in thefinallyblock on every invocation. Because each call tostatsDataproduces a newBetterSqlite3Databaseobject reference, the WeakMap key is always unique — the cache always misses anddb.prepare()is called every time.cachedStmtis only effective when the samedbobject is reused across multiple calls (e.g. a long-lived connection in MCP server mode). SincebuildTestFileIdsis not exported andstatsDataalways opens-and-closes, the optimisation stated in the PR description ("reused across calls") does not materialise in practice.The code is still functionally correct and consistent with the rest of the codebase's caching pattern — it is future-proof if
statsDatais ever refactored to accept an externaldbargument. But as written, bothdb.prepare()calls still execute on every invocation, so no performance gain is achieved.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.
Acknowledged — you're right that \ opens a fresh DB per call, so the cache doesn't hit in the current path. The change is intentionally forward-compatible: if \ or a future caller is refactored to accept a long-lived , the caching will activate automatically. Meanwhile it's a no-op with zero cost (WeakMap entry is immediately GC-eligible). Keeping for consistency with the rest of the codebase's \ pattern.