Mnemontron

Measured results and limits

All figures below are internal benchmarks run by the Mnemontron team in a development environment. They have not been independently reproduced. Each is reported with its setting; please do not compare them with numbers measured in a different setting.

Retrieval

MeasurementSettingResult
Recall at 20 (BM25)Natural Questions test, n=3,588, over 21,015,324 Wikipedia passages58.5%
Recall at 100 (BM25)Same run72.16%
Fast-path latencySame run, median / 95th percentile49.3 ms / 105 ms
Multi-hop recall at 20FRAMES, n=79414.36%

For reference, Karpukhin et al. (EMNLP 2020, Table 2) report BM25 recall at 20 of 59.1% on a 21M-passage Wikipedia setting. That was a different run, and we cite it only as context, not as a like-for-like comparison.

Answering and abstention

MeasurementSettingResult
Answerable questions answeredInternal held-out set, N=213 (101 answerable)90.1% (91 of 101)
Unanswerable questions correctly declinedSame set (112 unanswerable)88.4% (99 of 112)
Query latencySame set, median / 95th percentile40.3 ms / 53.3 ms

The held-out set was built internally. It is not a customer task set.

Storage and recovery

MeasurementSettingResult
Erasure-coded repair10,000 evidence objects, Reed-Solomon 4+2 across 6 buckets, one bucket dropped10,000 of 10,000 repaired and verified
Disaster-recovery restore50,000 evidence objects and claims restored into a fresh stackRecovery time 101.6 s
Ingest with dense vectors500,000-item ingest, all items embeddedCompleted

Capacity model

Mnemontron includes a capacity model for scenarios up to 100+ exabytes. It is a projection built from the measurements above and architectural assumptions. It is not a test that was run, and no projected latency or cost should be read as a measured result.

Not measured yet