Benchmark numbers only mean something when the measured job is named.
Someone asks whether a cold disk fetch, local warm read, and network command can be compared as one “database speed” number. They cannot. The path label is part of the claim.Warm
The needed local pages are available and the read shape is known.
≠
Cold
The machine still has storage or setup work before bytes are ready.
≠
Network
The request crosses a network before the app sees the result.
The categories
Warm local read = the needed data is already local, the operating system already has the needed file pages ready, and Bitfield has the read address.Cold local read = the data is local, but the machine still has setup or fetch work to do before the bytes are ready.Content address lookup = Bitfield first resolves the content identity, then reads the bytes.Durable batch write = Bitfield records a batch of writes in the durable write path, then the benchmark divides the batch cost across the written items.Runtime call = app code asks a Bitfield target to do work through Runtime Kit.Network command = a request crosses the network before the app gets an answer.Why the split matters
These jobs are different:If a row says one category, read it as that category. Do not silently turn it into another job.
The current public rows
Warm local read.The data is local and warm, so Bitfield can read known local bytes without sending a request to a separate database process.
Content address lookup.Bitfield first resolves the data fingerprint, then reads the bytes.
Durable batch write.The measured work includes the saved-write contract for a batch, then divides the batch cost across written items.
Batched write ceiling.This is a ceiling number for a full batch. It is not the same thing as every saved write.