NVIDIA H100 80GB HBM3 · median of 10 runs after 3 warm-ups · measured 2026-09-28T19:15:03+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, CUDA graphs1.31 mstransformers, compiled1.69 ms
- Linnet, ONNX Runtime f326.29 mstorch.onnx export6.38 ms
- Triton, Linnet's ONNX27.1 msTriton, torch.onnx export31.6 ms
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.
Latency
ms, lower is better; the best bar is red.
Throughput
/s, higher 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.
Every number
| Method | Latency | Throughput | Load time | Peak GPU memory | Against the stack it replaces | Distance from reference | Notes |
|---|---|---|---|---|---|---|---|
| PyTorch | |||||||
| transformers | 2.95 ms | 1,170/s | 6.78 s | 2.11 GiB | 0 (the reference) | ||
| transformers, compiled | 1.69 ms | 1,333/s | 3.67 s | 1.83 GiB | 1.53 | ||
| Linnet, generated PyTorch | 2.13 ms | 1,064/s | 1.13 s | 1.83 GiB | 0.79× transformers, compiled | 0.625 | |
| Linnet, inductor | 1.51 ms | 1,415/s | 1.29 s | 1.62 GiB | 1.12× transformers, compiled | 2.23 | |
| Linnet, CUDA graphs | 1.31 ms | 1,405/s | 1.18 s | 1.77 GiB | 1.29× transformers, compiled | 2.23 | |
| JAX | |||||||
| Linnet, XLA (StableHLO) | 2.50 ms | 603/s | 0.46 s | 3.34 GiB | 4.16 | bf16, like the torch rows; peak memory is JAX's allocator peak; the driver shows its pool, which grows in whole regions | |
| Linnet, XLA (generated JAX) | 2.26 ms | 1,137/s | 0.54 s | 1.26 GiB | 1.78 | bf16, like the torch rows; peak memory is JAX's allocator peak; the driver shows its pool, which grows in whole regions | |
| ONNX Runtime and TensorRT | |||||||
| torch.onnx export | 6.38 ms | 253/s | 17.3 s | 19.9 GiB | 1.09 | the reference model's own ONNX export, f32 like Linnet's; | |
| Linnet, ONNX Runtime f32 | 6.29 ms | 254/s | 0.30 s | 15.9 GiB | 1.01× torch.onnx export | 1.09 | f32; ONNX Runtime's CUDA execution provider; first calls build the sessions |
| Linnet, ONNX Runtime f16 | 3.95 ms | 452/s | 0.31 s | 8.42 GiB | 1.24 | f16; ONNX Runtime's CUDA execution provider; first calls build the sessions | |
| Linnet, ONNX Runtime bf16 | 4.92 ms | 355/s | 0.29 s | 8.47 GiB | 6.88 | bf16; ONNX Runtime's CUDA execution provider; first calls build the sessions | |
| Linnet, TensorRT f32 | 4.32 ms | 300/s | 0.28 s | 9.50 GiB | 1.09 | f32; ONNX Runtime's TensorRT execution provider; first calls build the sessions | |
| Linnet, TensorRT f16 | 1.16 ms | 1,471/s | 0.34 s | 9.15 GiB | 1.3 | f16; ONNX Runtime's TensorRT execution provider; first calls build the sessions | |
| Linnet, TensorRT bf16 | 1.26 ms | 1,412/s | 0.28 s | 9.15 GiB | 1.03 | bf16; ONNX Runtime's TensorRT execution provider; first calls build the sessions | |
| Triton Inference Server | |||||||
| Triton, torch.onnx export | 31.6 ms | 48.8/s | 12.0 s | 19.9 GiB | 1.03 | over HTTP; f32; throughput with 4 requests of batch 32 in flight | |
| Triton, Linnet's ONNX | 27.1 ms | 47.3/s | 15.0 s | 19.9 GiB | 1.17× Triton, torch.onnx export | 1.03 | over HTTP; f32; throughput with 4 requests of batch 32 in flight |
| Triton, Linnet Python backend | 25.6 ms | 47.7/s | 6.02 s | 3.86 GiB | 1.05 | over HTTP; bf16, CUDA graphs; throughput with 4 requests of batch 32 in flight | |