strata→signal speed the speeds we measured, played back

How fast is 136.3 tokens a second?

Press Start to watch an AI's answer appear at this speed. Change any number, or fill them in from a graphics card we tested.

The playback needs JavaScript. Without it, every card and model we tested is in the table below, with its numbers.

What this page is, and is not
  • This plays an answer back at a steady rate: the wait first, then the writing. A real model's stream is not steady, and real use moves it: the question's length, how full the window is, other people on the same card, the power limit, the weights and the cache, the engine and its version, heat, and the tokenizer.
  • A pick fills the three boxes from one run we measured: of our runs of that card, model and engine that measured the most of the three numbers, the one in the middle by writing speed (with an even number, the slower of the two in the middle). Nothing is averaged, so every number a pick shows was measured. A wait we measured is played as it is; where we measured none, the wait is worked out from the reading speed and the question's length, and the page says so.
  • "Skip the wait" moves one clock for both speeds at once, so neither can run ahead; the clock stops while this tab is hidden and starts again where it was.
  • The two texts. Prose is the opening of Reading is fast, writing is slow — why AI answers arrive word by word (published 2026-08-19), one of our own articles, word for word with its emphasis marks dropped. Code is parse_value from this tool's own source, the function that reads each figure from our results table, as it stood at commit b22e8980637b. Each speed splits the text with its model's own tokenizer where we know it; across the 8 tokenizers this page carries, the prose splits into 415 to 420 tokens (the most is 1.2% more than the fewest) and the code into 402 to 484 (20.4%). Every split is on the data page, with the file it came from.
  • This site makes no third-party requests — no fonts, no analytics, no CDN. Your browser talks to our server, and no one else's. After this page loads, its security policy refuses every request it could make — to anyone, including us; a navigation happens only when you click a link. The web server keeps its ordinary log line for each fetch, for 30 days, under the same rule as every page of the research hub: the time, the page asked for, the internet address it came from, and the headers the request carried, among them what kind of browser it is, its language and the page that linked here. The rule deletes cookies, credentials and the five common forwarding-address headers a proxy adds, and cuts any query from the address and from the linking page; Where your question goes says more. The numbers you type and the card you pick stay in this tab until you copy the link; then they sit after the # in the address, which a browser never sends to a server. When you copy the link, the page puts it in the address bar too: your browser keeps that address in its own history (a browser that syncs its history or open tabs to an account sends it there), and anyone you share the link with, and the app you share it through, can read it.
  • New hardware appears here when its rows publish on the research hub's hardware roster and a reviewed line names its card.

elsewhere in the workshop

RuleSageRealKeepambleResearchstudioprint labthe long tablethe playgroundthe whole family →
CallHomeSharpSignalKilnmemoryagencyeaselbrainkeelforge

a strata→signal property · hello@strata2signal.com · say hello