Aan de slagLeaderboardDecode calculatorModellenOrganizationsReportsMatrix runsHardwareBenchmarksMarktplaatsVerhuurProAPI Docs
Taal
Actual Computer — Every computer, one endpoint

Speed test matrix

GLM-5.3-MXFP4 on H200 SXM 141GB ×8

vllm · 0.29.0 · MXFP47 contexts (8K–507K) × 8 concurrency levels (1–128) · prefill at 8K, 16K, 32K, 64K, 128K, 256K, 507K, 512K
by @keennaylmx dev importMeasured

Hardware

Type
Discrete GPU
GPU
H200 SXM
GPU count
8
VRAM
1128 GB (8 × 141 GB)
OS
linux

Engine

Engine
vllm
Version
0.29.0
Quantization
MXFP4
Backend
cuda
Build
cuda-13.2

Run

Served model
glm
Revision
main
Decode test
Fixed duration
Prefill mode
Measured during decode warm-up
Time per measurement
30 s
Max output
4,096 tokens

Launch command

"$HOME/env_h200-glm53-vllm-v0290/bin/vllm" serve RedHatAI/GLM-5.3-MXFP4 --served-model-name glm --tensor-parallel-size 8 --reasoning-parser glm45 --enable-auto-tool-choice --tool-call-parser glm47 --max-model-len 524288 --gpu-memory-utilization 0.88 --host 0.0.0.0 --port 8000 --api-key <redacted> --dtype bfloat16 --kv-cache-dtype bfloat16 --no-enable-flashinfer-autotune

Prefill

prompt tok/s by context length
8K context8,942917 ms TTFT
16K context8,9001,823 ms TTFT
32K context8,7323,701 ms TTFT
64K context8,3697,709 ms TTFT
128K context7,70016,739 ms TTFT
256K context6,54539,364 ms TTFT
507K context5,037101,265 ms TTFT
512K context5,026102,486 ms TTFT

Sustained decode

total tok/s · rows are context length, columns are simultaneous requests
Context1248163264128
8K95.450 ms TTFT180.370 ms TTFT326.288 ms TTFT559.6130 ms TTFT938.8208 ms TTFT1,459.2325 ms TTFTOver capacityOver capacity
16K95.272 ms TTFT180.4102 ms TTFT326.0147 ms TTFT558.5216 ms TTFT934.6319 ms TTFT1,445.7543 ms TTFTOver capacityOver capacity
32K94.9113 ms TTFT179.4153 ms TTFT323.8201 ms TTFT560.1322 ms TTFT924.0559 ms TTFTOver capacityOver capacityOver capacity
64K94.4193 ms TTFT178.7259 ms TTFT321.7360 ms TTFT553.3593 ms TTFTOver capacityOver capacityOver capacityOver capacity
128K93.5371 ms TTFT176.4489 ms TTFT317.6708 ms TTFTOver capacityOver capacityOver capacityOver capacityOver capacity
256K91.9738 ms TTFT173.1997 ms TTFTOver capacityOver capacityOver capacityOver capacityOver capacityOver capacity
507K89.11,769 ms TTFTOver capacityOver capacityOver capacityOver capacityOver capacityOver capacityOver capacity

Over capacity: not run because this many requests at this context would exceed the server's KV cache.

TTFT is measured after the benchmark warms the server's prompt cache, so it mostly excludes prefill.

All measurements

Latencies are medians. Total tok/s is output across all simultaneous requests.
PhaseContextRequests at onceStatusTotal tok/sPer request tok/sTTFTTime between tokensAverage active requestsCompleted requestsOutput tokensMeasured for
Prefill8K1Valid8,942.0—917 ms——1——
Prefill16K1Valid8,900.0—1,823 ms——1——
Prefill32K1Valid8,732.0—3,701 ms——1——
Prefill64K1Valid8,369.0—7,709 ms——1——
Prefill128K1Valid7,700.0—16,739 ms——1——
Prefill256K1Valid6,545.0—39,364 ms——1——
Prefill507K1Valid5,037.0—101,265 ms——1——
Prefill512K1Valid5,026.0—102,486 ms——1——
Sustained decode8K1Valid95.495.350 ms10.5 ms1.002,86130.0 s
Sustained decode8K2Valid180.390.270 ms11.1 ms2.005,41030.0 s
Sustained decode8K4Valid326.281.688 ms12.2 ms4.009,78430.0 s
Sustained decode8K8Valid559.670.1130 ms14.3 ms8.0016,78430.0 s
Sustained decode8K16Valid938.858.8208 ms17.0 ms16.0028,15630.0 s
Sustained decode8K32Valid1,459.245.7325 ms21.9 ms32.0043,77330.0 s
Sustained decode8K64Over capacity————————
Sustained decode8K128Over capacity————————
Sustained decode16K1Valid95.295.272 ms10.5 ms1.002,85430.0 s
Sustained decode16K2Valid180.490.2102 ms11.1 ms2.005,41230.0 s
Sustained decode16K4Valid326.081.5147 ms12.3 ms4.009,77630.0 s
Sustained decode16K8Valid558.570.0216 ms14.3 ms8.0016,75130.0 s
Sustained decode16K16Valid934.658.4319 ms17.1 ms16.0028,03230.0 s
Sustained decode16K32Valid1,445.745.1543 ms22.2 ms32.0043,36030.0 s
Sustained decode16K64Over capacity————————
Sustained decode16K128Over capacity————————
Sustained decode32K1Valid94.995.0113 ms10.5 ms1.002,84730.0 s
Sustained decode32K2Valid179.489.7153 ms11.1 ms2.005,38230.0 s
Sustained decode32K4Valid323.881.0201 ms12.4 ms4.009,71230.0 s
Sustained decode32K8Valid560.169.9322 ms14.3 ms8.0016,80030.0 s
Sustained decode32K16Valid924.057.6559 ms17.4 ms16.0027,71230.0 s
Sustained decode32K32Over capacity————————
Sustained decode32K64Over capacity————————
Sustained decode32K128Over capacity————————
Sustained decode64K1Valid94.494.5193 ms10.6 ms1.002,83330.0 s
Sustained decode64K2Valid178.789.4259 ms11.2 ms2.005,35930.0 s
Sustained decode64K4Valid321.780.4360 ms12.4 ms4.009,65130.0 s
Sustained decode64K8Valid553.369.0593 ms14.5 ms8.0016,60030.0 s
Sustained decode64K16Over capacity————————
Sustained decode64K32Over capacity————————
Sustained decode64K64Over capacity————————
Sustained decode64K128Over capacity————————
Sustained decode128K1Valid93.593.6371 ms10.7 ms1.002,80430.0 s
Sustained decode128K2Valid176.488.3489 ms11.3 ms2.005,29030.0 s
Sustained decode128K4Valid317.679.4708 ms12.6 ms4.009,52930.0 s
Sustained decode128K8Over capacity————————
Sustained decode128K16Over capacity————————
Sustained decode128K32Over capacity————————
Sustained decode128K64Over capacity————————
Sustained decode128K128Over capacity————————
Sustained decode256K1Valid91.992.2738 ms10.8 ms1.002,75830.0 s
Sustained decode256K2Valid173.186.7997 ms11.5 ms2.005,19230.0 s
Sustained decode256K4Over capacity————————
Sustained decode256K8Over capacity————————
Sustained decode256K16Over capacity————————
Sustained decode256K32Over capacity————————
Sustained decode256K64Over capacity————————
Sustained decode256K128Over capacity————————
Sustained decode507K1Valid89.189.61,769 ms11.2 ms1.002,67330.0 s
Sustained decode507K2Over capacity————————
Sustained decode507K4Over capacity————————
Sustained decode507K8Over capacity————————
Sustained decode507K16Over capacity————————
Sustained decode507K32Over capacity————————
Sustained decode507K64Over capacity————————
Sustained decode507K128Over capacity————————

Over capacity: not run because this many requests at this context would exceed the server's KV cache.