Skip to content

docs(search): EmbeddingGemma on Drive documents; vector search time at volume - #41

Open
leemour wants to merge 3 commits into
mainfrom
docs/gemma-drive-result
Open

leemour wants to merge 3 commits into
mainfrom
docs/gemma-drive-result

Conversation

@leemour

@leemour leemour commented Oct 13, 2026

Copy link
Copy Markdown
Contributor

Completes the vectors-only comparison on performance/search/local-documents (owner decision NEED-1002 A).

Drive, 25 queries hit@1 hit@3 hit@10 MRR@10 embedding
e5-small vectors 0.48 0.76 0.76 0.60 9 min
EmbeddingGemma vectors 0.80 0.84 0.96 0.85 2 h 28 min
drive, words and meaning (e5-small fused) 0.68 0.80 0.92 0.76 —

One run, 25 queries; fusion of EmbeddingGemma with the word list not measured. Per-query rows stay in cli-private.

🤖 Generated with Claude Code

EmbeddingGemma vectors alone put the right Drive document first in 0.80 of 25 queries against e5-small's
0.48 and drive's fused search's 0.68, at 2 h 28 min of embedding against 9 min. rerank.mjs takes
PASSAGES_OVERRIDE for a document edited after its vectors were made.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@leemour leemour changed the title docs(search): EmbeddingGemma against e5-small on Drive documents docs(search): EmbeddingGemma on Drive documents; vector search time at volume Oct 13, 2026
leemour and others added 2 commits October 13, 2026 22:02
Brute-force search reading vectors from SQLite in pages of 5,000: 33 ms, 271 ms, 821 ms — linear, about
2.7 ms per 1,000 vectors. Answers whether one embeddings table slows search at volume.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

This branch has not been deployed

No deployments
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