perf: Improve novelty and property-path query performance#1239
Merged
Conversation
…y subjects before binary scans and allowing three-predicate star patterns to use the property-join path
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.
Resolve novelty-only subjects during binary scans so recent writes can use constrained lookups.
Enable property joins for exact-threshold star patterns, improving vector similarity query plans.
Short-circuit bound property-path reachability checks once the target is found.
Manual benchmark: vector query improved from ~36s to ~720ms warm; bounded inverse
^storage:parent+folder query runs in ~750-860ms warm versus forwardstorage:parent+timing out through CloudFront.