Skip to content

research(nightly): gnn-rerank — GNN score diffusion +10.4 pp recall@10#479

Draft
ruvnet wants to merge 6 commits into
mainfrom
research/nightly/2026-05-21-gnn-rerank
Draft

research(nightly): gnn-rerank — GNN score diffusion +10.4 pp recall@10#479
ruvnet wants to merge 6 commits into
mainfrom
research/nightly/2026-05-21-gnn-rerank

Conversation

@ruvnet
Copy link
Copy Markdown
Owner

@ruvnet ruvnet commented May 21, 2026

Nightly RuVector Research — 2026-05-21 — GNN-Enhanced Candidate Reranking

Adds nightly research for gnn-rerank: graph neural score diffusion over
approximate ANN candidate sets.

Includes

  1. Working Rust PoCcrates/ruvector-gnn-rerank

    • CandidateReranker trait with 4 variants (NoisyScore, GnnDiffusion, GnnMincut, ExactL2)
    • 14 passing unit tests
    • Benchmark binary with real measured results
  2. ADRdocs/adr/ADR-194-gnn-rerank.md

  3. Research documentdocs/research/nightly/2026-05-21-gnn-rerank/README.md

  4. Public gistdocs/research/nightly/2026-05-21-gnn-rerank/gist.md

Real benchmark numbers (x86-64, Linux 6.18.5, rustc 1.87.0, N=5K, D=128, K=10)

Variant recall@10 mean µs Throughput
NoisyScore (baseline) 28.0% 0.2 4.9M QPS
GnnDiffusion (1-hop) 38.4% 1006 994 QPS
GnnMincut (coh≥0.50) 38.4% 999 1001 QPS
ExactL2 (oracle) 74.9% 13.8 72.5K QPS

GNN score diffusion: +10.4 pp recall@10. Acceptance: PASS ✓

Build

cargo build --release -p ruvector-gnn-rerank  # GREEN
cargo test -p ruvector-gnn-rerank              # 14/14 passed
cargo run --release -p ruvector-gnn-rerank --bin benchmark  # PASS ✓

Main lesson

Graph score diffusion is cheap (~1ms overhead) and measurably effective (+10.4 pp).
ExactL2 reranking is faster (14µs) when full-precision candidates are available locally.
GNN diffusion's value is highest when candidate vectors must be fetched or are stored compressed.

This branch should either become a production RuVector capability or a falsified research path with useful evidence.


Generated by Claude Code

claude added 6 commits May 21, 2026 07:31
SOTA scan: graph-based reranking is a validated 2025-2026 direction
(GNRR +5.8pp AP, Maniscope +7pp NDCG, AQR-HNSW 2.5-3.3x QPS).
No production Rust vector DB applies GNN message passing over ANN
candidate subgraph topology. Introduces this as the nightly research
topic and documents ten candidate alternatives with scoring formula.
Implements CandidateReranker trait with four variants:
  - NoisyScoreReranker: passthrough baseline (28.0% recall@10)
  - GnnDiffusionReranker: 1-hop score averaging (+10.4 pp → 38.4%)
  - GnnMincutReranker: structurally-gated diffusion (38.4%)
  - ExactL2Reranker: oracle upper bound (74.9%)

All files < 500 lines. No unsafe code. No external service dependency.
Tests cover: graph degree bounds, self-not-in-neighbours invariant,
ExactL2 correctness, error conditions (empty/k-too-large),
all three reranker variants produce k results.
All 14 pass: cargo test -p ruvector-gnn-rerank.
Hardware: x86-64, Intel Celeron N4020, Linux 6.18.5, rustc 1.87.0
N=5000, D=128, clusters=20, K=10, retrieval_k=80, noise_sigma=0.40

NoisyScore (baseline):  28.0% recall@10,   0.2 µs,  4.9M QPS
GnnDiffusion (1-hop):   38.4% recall@10, 1006 µs,   994 QPS  +10.4 pp
GnnMincut (coh≥0.50):   38.4% recall@10,  999 µs,  1001 QPS  +10.4 pp
ExactL2 (oracle):       74.9% recall@10,  13.8 µs, 72.5K QPS

Candidate coverage: 74.9%. Acceptance: PASS.
Records architecture decision: CandidateReranker trait, four variants,
graph construction design, acceptance of structural coherence gating
over score-ratio gating, benchmark evidence, failure modes, open questions.
Public technical article covering:
- GNN score diffusion algorithm and three variants
- Real benchmark table from cargo run --release
- Comparison with Milvus, Qdrant, Weaviate, LanceDB, FAISS, pgvector
- 10 practical + 8 exotic applications
- Roadmap: now/next/later
- 11 cited arXiv papers (2024-2026)
- 25 SEO keywords + GitHub topic tags
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.

2 participants