Checking…
How long each model took to answer, run by run. Switch to vs. its own normal to see each model as a percentage of its own median, which is how the verdict above is decided. A hollow dot means the response came back empty or was refused.
Each model's latest response time, compared with its own recent runs. Typical is the median of that model's earlier runs in the selected range.
The latest run from each model, split into time spent waiting for the first word and time spent writing.
Every model gets the same prompt on a schedule, and we time the reply. Nothing is executed and nothing is graded.
—) is
stored on every run, so any edit to it shows up in the data.
The clock is split three ways. Time up to the first byte of the response
covers network round-trip, TLS, and any queueing before the provider starts replying. From
there to the first visible word, the model is thinking. After that it is
writing.
Network transit and provider queueing cannot be separated inside that first segment, since
both finish before the server sends anything. From a single region it stays a small and
fairly stable slice.
Medians across the selected range. Two caveats: rate is not
generation speed for models that reason silently and then send the answer at once, and
output tokens are not comparable between Opus 4.6 and 4.7+ (different
tokenizers). Every model runs at medium effort with adaptive thinking.