The record of a build
Chunks, bytes, and the time. The record is what a size claim and a speed claim are checked against.
The library is larger than the memory. The index is built in pieces, and the pieces are the reason a large library is possible at all.
About 1 min of reading
Chunk to a limit and record
Write the memory limit
Before you run it, say out loud what it will print. Then open the answer.
Write the chunks
Before you run it, say out loud what it will print. Then open the answer.
Record the restart point
Before you run it, say out loud what it will print. Then open the answer.
Chunks, bytes, and the time. The record is what a size claim and a speed claim are checked against.
Documents differ in size. A byte limit is a limit on the thing that is actually counted, which is memory.
A chunk is built until the limit, then written and released. Released is the word that makes the next chunk possible.
Two chunks with the same key become one posting. One walk over sorted keys is the merge, and the walk is the cost.
The last chunk written is recorded. Recorded means a failed build restarts at the chunk rather than at the start.
Each one is defined here on this site. Open the entry for the full definition and the other words it points at.