Build · 22 May 2026

Mean fanout measured at 2.60

One to three reads per lookup, which is what makes a memory-mapped artefact viable.

Mean fanout
2.60
Reads
1 to 3
Build
9d1c40b7
Basis
Measured

Specifics

The numbers, and where they come from

Figures on this page, with the basis of each
QuantityValueBasis
Mean fanout2.60Measured
Reads per lookup1 to 3Measured
Corpus40,000 held-out sentencesCounted
Worst case observed5 readsMeasured
1 read41%2 reads34%3 reads19%4 or more6%
Distribution of reads per lookup. The tail is what a memory-mapped design has to survive.

The measurement

Why fanout is the number that matters

Fanout is how many index nodes a lookup touches before it resolves. On a memory-mapped artefact each of those is potentially a page fault, so the mean determines whether Folio is viable on a machine with a disk rather than only on one with the whole artefact in RAM.

Measured at 2.60 across the held-out set. Ninety-four per cent of lookups resolve in three reads or fewer.

What it does not tell you

A mean is not a guarantee

The mean is comfortable and the tail is what will hurt you. Six per cent of lookups take four reads or more, and on a cold page cache those are the ones a latency budget notices.

This is why the response figure is quoted with the artefact already mapped, and why that qualifier appears every time the figure does.