Skip to content

Option 1: prefetch NaviX bridge traversal - #1119

Draft
lerman25 wants to merge 1 commit into
omer-navix-traversal-pocfrom
omer-navix-auto-latency-poc
Draft

lerman25 wants to merge 1 commit into
omer-navix-traversal-pocfrom
omer-navix-auto-latency-poc

Conversation

@lerman25

@lerman25 lerman25 commented Nov 12, 2026 •

Copy link
Copy Markdown
Collaborator

Describe the changes in the pull request

NaviX bridge traversal reads vector and graph data without the prefetching used by ordinary HNSW batches. Prefetch upcoming vector/visited data and the current node's graph/metadata while retaining traversal order, filtering, timeout checks, and batch continuation. This is an internal POC optimization measured alongside RediSearch's selectivity-aware policy.

Stacked on #1116. The existing stable graph/label/filter-view restriction remains. Eleven focused NaviX tests passed locally; no production or concurrent-update claim.

Combined-policy results are recorded in RediSearch/RediSearch#12323: three paired 10,000-query passes show 45.32 → 29.95 ms mean latency and 216.56 → 119.62 ms p99, at 96.28% → 98.12% recall. Median latency regresses 8.0%, and only 37.95% of query IDs improve. This experiment does not isolate prefetch's contribution. VecSim CI currently fails before compilation because the Ubuntu 26.04 installer script is missing; the 11 focused local tests passed.

Which issues this PR fixes

N/A

Main objects this PR modified

  1. RAM HNSW batch iterator: prefetch data in the experimental NaviX path.

Mark if applicable

  • This PR introduces API changes
  • This PR introduces serialization changes

@lerman25 lerman25 changed the title POC: prefetch NaviX bridge traversal data Option 1: prefetch NaviX bridge traversal Nov 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant