Free tool · source benchmarks
Look up measured tokens per second
Find measured tokens per second for a model and GPU or Mac. Compare separate model sizes, workloads and reported settings before estimating what your setup might deliver. Every displayed rate links to its source.
Llama-3.1-8B-Instruct on RTX 5090
5 measured workload rows from 2 source runs, separated into 5 reported-settings groups. Choose the size, workload and settings closest to yours. Each range describes its included rows; it is not a forecast or confidence interval.
Size not reported · chat-short · Quant not reported229.4tok/s observed median · 1 row / 1 run
RTX 5090 (32GB)
llama.cpp (version not reported) · suite suite-v1 · client 0.0.3
Batch: 1 · context: 0 tokens · input/output: 0/256 tokens.
Observed range: 229.4tok/s–229.4tok/s.
- r_qr4srge34da229.4tok/s · first token 35.6ms
Size not reported · chat-long · Quant not reported211.4tok/s observed median · 1 row / 1 run
RTX 5090 (32GB)
llama.cpp (version not reported) · suite suite-v1 · client 0.0.3
Batch: 1 · context: 0 tokens · input/output: 0/351 tokens.
Observed range: 211.4tok/s–211.4tok/s.
- r_qr4srge34da211.4tok/s · first token 266ms
Size not reported · concurrent-decode · Quant not reported223.0tok/s observed median · 1 row / 1 run
RTX 5090 (32GB)
llama.cpp (version not reported) · suite suite-v1 · client 0.0.3
Batch: 1 · context: 1024 tokens · input/output: 1024/256 tokens.
Observed range: 223.0tok/s–223.0tok/s.
- r_qr4srge34da223.0tok/s · first token no data
Size not reported · agent-trace · Quant not reported210.3tok/s observed median · 1 row / 1 run
RTX 5090 (32GB)
llama.cpp (version not reported) · suite suite-v1 · client 0.0.3
Batch: 1 · context: 3362 tokens · input/output: 3362/840 tokens.
Observed range: 210.3tok/s–210.3tok/s.
- r_qr4srge34da210.3tok/s · first token 60.8ms
Size not reported · chat-short · Quant not reported232.2tok/s observed median · 1 row / 1 run
RTX 5090 (32GB)
llama.cpp (version not reported) · suite suite-v1 · client 0.0.3
Batch: 1 · context: 0 tokens · input/output: 0/256 tokens.
Observed range: 232.2tok/s–232.2tok/s.
- r_kfrkg-vn376232.2tok/s · first token 33.8ms
How to estimate LLM speed from benchmarks
Start with the same model size, quantization, hardware configuration and runtime. Then match the workload, batch size and actual token lengths. A short chat result does not establish speed for a long prompt or several simultaneous users.
Try a measured configuration
Tokens per second and waiting time answer different questions
Decode tok/s measures token generation speed. First-token latency captures the wait before generation starts. Keep both alongside input and output lengths when comparing a chat or coding workflow. Tokenizers differ, so equal token rates do not guarantee equal useful work.
What the groups mean
This lookup includes successful positive decode measurements from matching model and hardware families in up to the latest 500 listed submissions. Groups preserve reported model size, quantization, backend and version, hardware summary, suite/client versions, workload, batch, context and input/output lengths. Missing configuration fields keep separate source runs apart.
Matching reported fields does not prove identical prompts, model files, runtime flags or hardware. The median and minimum/maximum describe the included rows; they do not predict an unmeasured setup. Open the source run and use the methodology to assess comparability.
For a hardware purchase, check the memory estimator and tested model files as well. A fast submitted run alone does not establish that your chosen file and context will fit.
Full benchmark table · Contribute a measurement · Download benchmark data