NVIDIA H100 80GB HBM3 · 512 prompt tokens, 128 new · batch 1 · median of 10 runs after 3 warm-ups · measured 2026-09-28T17:48:44+00:00
Linnet 0.1.0, PyTorch 2.14.0, JAX 0.11.2, transformers 5.17.0, diffusers 0.40.0, ONNX Runtime 1.30.0, Python 3.12.3, driver 580.126.09
Linnet against the stack it replaces
Each side in its fastest configuration, on the same GPU and checkpoint. A speed-up is how many times the other's speed; an export is measured against the original checkpoint in the same engine.
- Linnet, XLA (generated JAX)255 tok/svLLM230 tok/s
- Linnet, CUDA graphs247 tok/stransformers, compiled123 tok/s
- Linnet, XLA (generated JAX)255 tok/sKerasHub227 tok/s
- vLLM on Linnet's export236 tok/svLLM230 tok/s
- linnet.serve, CUDA graphs8,196 tok/svLLM8,048 tok/s
- vLLM on Linnet's export8,158 tok/svLLM8,048 tok/s
- Triton, linnet.serve backend7,786 tok/sTriton, vLLM backend2,082 tok/s
Each row also carries its distance from reference: the largest absolute difference between its output and transformers (eager)'s on the same input. bf16 outputs differ by rounding (about 0.1 on logits near 16), so a small number is expected; it is there so that a fast wrong answer cannot look like a win.
Time to first token
ms, lower is better; the best bar is red.
Decode speed
tok/s, higher is better; the best bar is red.
Serving throughput
tok/s, higher is better; the best bar is red.
Serving time to first token
ms, lower is better; the best bar is red.
Load time
s, lower is better; the best bar is red.
Peak GPU memory
What the driver reports the process holding at its peak, in GiB; lower is better; the best bar is red. Not drawn, since theirs is a setting rather than a need: vLLM, vLLM, transformers, batched, Triton, vLLM backend, vLLM on Linnet's export, vLLM on Linnet's export (in the table).
Every number
| Method | Time to first token | Decode speed | Serving throughput | Serving time to first token | Load time | Peak GPU memory | Against the stack it replaces | Distance from reference | Notes |
|---|---|---|---|---|---|---|---|---|---|
| PyTorch | |||||||||
| transformers | 20.7 ms | 50.0 tok/s | – | – | 5.74 s | 8.58 GiB | 0 (the reference) | ||
| transformers, compiled | 13.2 ms | 123 tok/s | – | – | 2.71 s | 8.69 GiB | 0.125 | ||
| Linnet, generated PyTorch | 14.5 ms | 72.2 tok/s | – | – | 1.90 s | 9.14 GiB | 0.59× transformers, compiled | 0.0938 | KV cache compiled for 768 positions |
| Linnet, inductor | 8.71 ms | 168 tok/s | – | – | 1.79 s | 12.4 GiB | 1.36× transformers, compiled | 0.188 | KV cache compiled for 768 positions |
| Linnet, CUDA graphs | 7.64 ms | 247 tok/s | – | – | 1.83 s | 12.5 GiB | 2.00× transformers, compiled | 0.188 | KV cache compiled for 768 positions |
| JAX | |||||||||
| KerasHub | 24.6 ms | 227 tok/s | – | – | 17.0 s | 10.0 GiB | 0.125 | peak memory is JAX's allocator peak; the driver shows its pool, which grows in whole regions | |
| Linnet, XLA (StableHLO) | 14.6 ms | 254 tok/s | – | – | 5.04 s | 9.19 GiB | 1.12× KerasHub | 0.0938 | KV cache compiled for 768 positions; peak memory is JAX's allocator peak; the driver shows its pool, which grows in whole regions |
| Linnet, XLA (generated JAX) | 13.2 ms | 255 tok/s | – | – | 4.85 s | 9.19 GiB | 1.12× KerasHub | 0.188 | KV cache compiled for 768 positions; peak memory is JAX's allocator peak; the driver shows its pool, which grows in whole regions |
| ONNX Runtime and TensorRT | |||||||||
| Linnet, ONNX Runtime f32 | 38.6 ms | 59.4 tok/s | – | – | 0.42 s | 20.3 GiB | 0.155 | f32; ONNX Runtime's CUDA execution provider; first calls build the sessions; logits copied to the host each step for the argmax | |
| Linnet, ONNX Runtime f16 | 30.1 ms | 68.7 tok/s | – | – | 0.45 s | 10.6 GiB | 0.672 | f16; ONNX Runtime's CUDA execution provider; first calls build the sessions; logits copied to the host each step for the argmax | |
| Linnet, ONNX Runtime bf16 | 32.1 ms | 67.4 tok/s | – | – | 0.42 s | 10.00 GiB | 0.5 | bf16; ONNX Runtime's CUDA execution provider; first calls build the sessions; logits copied to the host each step for the argmax | |
| Linnet, TensorRT f32 | 35.9 ms | 45.6 tok/s | – | – | 0.42 s | 44.8 GiB | 0.153 | f32; ONNX Runtime's TensorRT execution provider; first calls build the sessions; logits copied to the host each step for the argmax | |
| Linnet, TensorRT f16 | 19.5 ms | 72.2 tok/s | – | – | 0.41 s | 23.6 GiB | 11.4 | f16; ONNX Runtime's TensorRT execution provider; first calls build the sessions; logits copied to the host each step for the argmax | |
| Linnet, TensorRT bf16 | 19.3 ms | 69.7 tok/s | – | – | 0.43 s | 23.1 GiB | 0.406 | bf16; ONNX Runtime's TensorRT execution provider; first calls build the sessions; logits copied to the host each step for the argmax | |
| LLM engines | |||||||||
| vLLM | 11.5 ms | 230 tok/s | – | – | 95.5 s | 68.0 GiB | not compared | reserves a KV-cache pool up front (gpu_memory_utilization 0.85), so its memory is a setting, not a need | |
| vLLM on Linnet's export | 7.47 ms | 236 tok/s | – | – | 68.4 s | 68.0 GiB | +2.4% from vLLM | not compared | linnet.hf.export (8 s), then vLLM on the exported checkpoint; reserves a KV-cache pool up front (gpu_memory_utilization 0.85), so its memory is a setting, not a need |
| llama.cpp on Linnet's GGUF | 17.5 ms | 250 tok/s | – | – | 29.8 s | 8.55 GiB | not compared | linnet.gguf.export, then llama-bench with every layer on the GPU; the first token is the prompt at llama-bench's prompt rate | |
| Serving many requests | |||||||||
| vLLM | – | – | 8,048 tok/s | – | 58.2 s | 68.4 GiB | not compared | 256 requests of 128-512 prompt tokens and 128 new tokens, at most 64 in flight; KV-cache pool at gpu_memory_utilization 0.85 | |
| linnet.serve, CUDA graphs | – | – | 8,196 tok/s | 1,666 ms | 5.11 s | 18.1 GiB | 1.02× vLLM | not compared | 256 requests of 128-512 prompt tokens and 128 new tokens, at most 64 in flight; 64 fixed cache rows of 640 positions |
| linnet.serve, XLA | – | – | 6,786 tok/s | 2,136 ms | 8.40 s | 15.2 GiB | 0.84× vLLM | not compared | 256 requests of 128-512 prompt tokens and 128 new tokens, at most 64 in flight; 64 fixed cache rows of 640 positions; peak memory is JAX's allocator peak; the driver shows its pool, which grows in whole regions |
| linnet.serve, ONNX Runtime | – | – | 4,203 tok/s | 3,644 ms | 0.26 s | 30.9 GiB | 0.52× vLLM | not compared | 256 requests of 128-512 prompt tokens and 128 new tokens, at most 64 in flight; 64 fixed cache rows of 640 positions |
| vLLM on Linnet's export | – | – | 8,158 tok/s | – | 50.2 s | 68.4 GiB | +1.4% from vLLM | not compared | linnet.hf.export (0 s), then vLLM (offline, continuous batching) on the exported checkpoint; 256 requests of 128-512 prompt tokens and 128 new tokens, at most 64 in flight; KV-cache pool at gpu_memory_utilization 0.85 |
| Triton, vLLM backend | – | – | 2,082 tok/s | 5,981 ms | 72.1 s | 67.9 GiB | not compared | 256 requests of 128-512 prompt tokens and 128 new tokens, at most 64 in flight; over HTTP, streamed, first tokens timed at the client | |
| Triton, linnet.serve backend | – | – | 7,786 tok/s | 1,747 ms | 659 s | 18.6 GiB | 3.74× Triton, vLLM backend | not compared | 256 requests of 128-512 prompt tokens and 128 new tokens, at most 64 in flight; over HTTP, streamed, first tokens timed at the client |
| transformers, batched | – | – | 850 tok/s | – | 2.31 s | 79.1 GiB | not compared | 256 requests of 128-512 prompt tokens and 128 new tokens, at most 64 in flight; paged|sdpa attention; reserves a paged KV-cache pool up front, so its memory is a setting, not a need; no per-request timestamps | |
| KerasHub, static batches | – | – | 384 tok/s | – | 17.6 s | 21.1 GiB | not compared | 256 requests of 128-512 prompt tokens and 128 new tokens, at most 64 in flight; every batch runs to the longest possible prompt plus the new tokens; peak memory is JAX's allocator peak; the driver shows its pool, which grows in whole regions | |