Files
ely-eye/bench/reports/CURRENT.md
T
ZacharyZhang-NY c4a8c36416 Put the scale evidence in the repo and say plainly what still misses
Every number in CHECKLIST p2-1 and p0-3.7 came out of a scratch script: the
kind of artifact a reader cannot re-run, and the kind that quietly drifts
away from the code it describes. These reports are generated by committed
harnesses and each one stamps the commit that carries the code it measures.

DENSE.md  165,973 atoms / 153,857 vectors: build 1421.0s, search p50 75.6ms
          p95 93.0ms, 0.998 agreement with a brute-force scan, one write into
          a full index p50 518ms, 1,729 bytes per stored vector.
QUANT.md  twelve encodings measured on the same vectors: int8 keeps 0.977 of
          the ranking for a quarter of the bytes and no speed, bit is 14x
          faster and keeps 0.728, so bit is a coarse filter and nothing more.
TERMS.md  the stop-word bound swept, not guessed: 0.05 is the measured peak
          (recall@10 0.803 at p50 69.5ms) and also the fastest of the rows
          that keep recall.
SCALE.md  the product's own search at 165,973 atoms: p50 71.7ms against the
          frozen baseline's 20.16s.
LEGS.md   what each retrieval leg is worth, per modality, with the page size
          the product actually asks for in the table.

The acceptance bar the operator set is recall@10 >= 0.90 at n>=300. It is
not met. The best measured row is 0.858 (dense leg on, page widened to 30,
p50 414ms); the shipped configuration gives 0.848 at p50 72.5ms; the
in-repo counterpart at holder scope gives 0.866. The shortfall is
concentrated in picture golds (video 0.583-0.708, ui_screenshot 0.500-0.583,
image 0.750) while the word-shaped ones already pass (code 0.953, pdf 0.919).
Latency passes by three hundred fold; recall does not, and the gap is four
points of cross-modal retrieval, not index scale.
2026-10-08 17:01:20 -04:00

3.2 KiB

CURRENT: what the product retrieves at this build

  • generated 2026-10-08T20:17:12+00:00 at commit dff5977ab6
  • measured store schema: v8
  • corpus 50278 sources, 5308 queries (2928 answerable)
  • models: dense sentence-transformers/paraphrase-multilingual-MiniLM-L12-v2, rerank BAAI/bge-reranker-base
  • machine: 32 cores, 4 threads per query, load average 5.1 when the report was written
arm recall@1 recall@5 recall@10 nDCG@10 MRR hit@10 (95% lower) p50 s p95 s
chance (random ranking) 0.000 0.000 0.000 - - - - -
bm25_only 0.313 0.465 0.519 0.415 0.383 0.524 (0.505) 0.563 3.141
dense_only 0.227 0.363 0.424 0.321 0.290 0.429 (0.411) 1.728 2.883
graph_only 0.000 0.001 0.001 0.000 0.000 0.001 (0.000) 0.043 0.058
no_rerank 0.342 0.510 0.565 0.452 0.418 0.571 (0.553) 2.404 5.169
fusion_rerank 0.236 0.391 0.453 0.341 0.309 0.459 (0.441) 4.538 9.043

recall@10 by modality

arm pdf image ui_screenshot video code conversation
bm25_only 0.704 0.637 0.322 0.126 0.518 0.368
dense_only 0.698 0.481 0.075 0.228 0.382 0.304
graph_only 0.000 0.000 0.000 0.000 0.002 0.000
no_rerank 0.742 0.669 0.297 0.153 0.592 0.447
fusion_rerank 0.253 0.692 0.300 0.088 0.629 0.486

unanswerable queries (44.8% of the suite)

  • bm25_only: abstains on 0% of unanswerable queries, and its top hit comes from the query's own holder for 38% of them; the rest are confident answers pulled out of somebody else's memory
  • dense_only: abstains on 0% of unanswerable queries, and its top hit comes from the query's own holder for 25% of them; the rest are confident answers pulled out of somebody else's memory
  • graph_only: abstains on 0% of unanswerable queries, and its top hit comes from the query's own holder for 0% of them; the rest are confident answers pulled out of somebody else's memory
  • no_rerank: abstains on 0% of unanswerable queries, and its top hit comes from the query's own holder for 40% of them; the rest are confident answers pulled out of somebody else's memory
  • fusion_rerank: abstains on 0% of unanswerable queries, and its top hit comes from the query's own holder for 34% of them; the rest are confident answers pulled out of somebody else's memory

the product path, asked as its holder

  • RetrievalService.search as the query's own holder: recall@10 0.832, MRR 0.683, hit@10 0.833 (95% lower 0.787) over n=300 answerable queries
  • latency p50 0.074s, p95 0.146s, mean 0.079s, max 0.314s
  • top-10 overlap with the fast BM25 path: 13.4%, identical order 0.0%
  • its top-10 atoms cover 5.2 distinct sources on average (min 0): the product ranks atoms and never diversifies, so ten slots can fill with fragments of one document

reading

  • recall counts a source as found only when it is the source a third party marked correct.
  • abstention is the only honest number for unanswerable queries: a retriever that always returns ten results never says it does not know.
  • chance is the floor any of these arms must beat; a number near chance is not a capability.