Primeros pasosClasificaciónDecode calculatorModelosOrganizationsReportsMatrix runsHardwareEvaluaciones comparativasMarketplaceAlquileresProDocs de API
Idioma
Actual Computer — Every computer, one endpoint

Speed test matrix

Laguna-XS.2-FP8 on RTX PRO 6000 Blackwell Server Edition 96GB

vllm · 0.30.1rc1.dev452+g73a583112 · FP86 contexts (8K–251K) × 8 concurrency levels (1–128) · prefill at 8K, 16K, 32K, 64K, 128K, 251K, 256K
by @keennaylmx dev importMeasured

Hardware

Type
Discrete GPU
GPU
RTX PRO 6000 Blackwell Server Edition
VRAM
96 GB
OS
linux

Engine

Engine
vllm
Version
0.30.1rc1.dev452+g73a583112
Quantization
FP8
Backend
cuda
Build
cuda-13.2
Commit
73a5831127a9

Run

Served model
poolside
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

env VLLM_BLOCKSCALE_FP8_GEMM_FLASHINFER=0 MAX_JOBS=2 FLASHINFER_NVCC_THREADS=1 TORCHINDUCTOR_COMPILE_THREADS=1 "$HOME/env_rtxpro6k-poolside-vllm-73a5831127a9/bin/vllm" serve poolside/Laguna-XS.2-FP8 --served-model-name poolside --trust-remote-code --tensor-parallel-size 1 --reasoning-parser poolside_v1 --enable-auto-tool-choice --tool-call-parser poolside_v1 --max-model-len 262144 --gpu-memory-utilization 0.81 --host 0.0.0.0 --port 8000 --api-key <redacted> --default-chat-template-kwargs '{"enable_thinking":true}' --attention-backend FLASHINFER --moe-backend triton

Prefill

prompt tok/s by context length
8K context37.1K221 ms TTFT
16K context34.7K467 ms TTFT
32K context29.5K1,092 ms TTFT
64K context22.3K2,881 ms TTFT
128K context14.8K8,685 ms TTFT
251K context8,95928,061 ms TTFT
256K context8,68829,513 ms TTFT

Sustained decode

total tok/s · rows are context length, columns are simultaneous requests
Context1248163264128
8K194.829 ms TTFT300.035 ms TTFT523.441 ms TTFT804.872 ms TTFT1,253.3131 ms TTFT1,839.2224 ms TTFT2,840.0464 ms TTFT4,315.4855 ms TTFT
16K190.042 ms TTFT294.049 ms TTFT516.457 ms TTFTLooped1,169.3208 ms TTFT1,693.4380 ms TTFT2,590.2618 ms TTFTOver capacity
32K181.567 ms TTFT286.075 ms TTFT489.676 ms TTFT723.5207 ms TTFT1,054.5359 ms TTFT1,455.5631 ms TTFTOver capacityOver capacity
64K166.9124 ms TTFT266.8144 ms TTFT459.5228 ms TTFT632.3382 ms TTFT874.4673 ms TTFTOver capacityOver capacityOver capacity
128K143.1245 ms TTFT239.8343 ms TTFT394.7480 ms TTFT505.6812 ms TTFTOver capacityOver capacityOver capacityOver capacity
251K113.3561 ms TTFT197.2754 ms TTFT316.71,164 ms TTFTOver capacityOver capacityOver capacityOver capacityOver capacity

Looped: the model kept repeating the same text, so the benchmark discarded this measurement. 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
Prefill8K1Valid37.1K—221 ms——1——
Prefill16K1Valid34.7K—467 ms——1——
Prefill32K1Valid29.5K—1,092 ms——1——
Prefill64K1Valid22.3K—2,881 ms——1——
Prefill128K1Valid14.8K—8,685 ms——1——
Prefill251K1Valid8,959.0—28,061 ms——1——
Prefill256K1Valid8,688.0—29,513 ms——1——
Sustained decode8K1Valid194.8195.129 ms5.1 ms1.015,84230.0 s
Sustained decode8K2Valid300.0150.535 ms6.6 ms2.028,99830.0 s
Sustained decode8K4Valid523.4133.241 ms7.5 ms4.0415,70030.0 s
Sustained decode8K8Valid804.8101.372 ms9.9 ms8.0024,14430.0 s
Sustained decode8K16Valid1,253.379.1131 ms12.6 ms16.0037,59830.0 s
Sustained decode8K32Valid1,839.258.3224 ms17.1 ms32.0055,16930.0 s
Sustained decode8K64Valid2,840.045.1464 ms22.2 ms64.0085,19930.0 s
Sustained decode8K128Valid4,315.434.5855 ms29.0 ms128.00129,46130.0 s
Sustained decode16K1Valid190.0190.542 ms5.3 ms1.015,69930.0 s
Sustained decode16K2Valid294.0147.849 ms6.8 ms2.028,81830.0 s
Sustained decode16K4Valid516.4130.557 ms7.7 ms3.9415,49030.0 s
Sustained decode16K8Looped—————00—
Sustained decode16K16Valid1,169.373.9208 ms13.5 ms16.0035,07230.0 s
Sustained decode16K32Valid1,693.453.6380 ms18.7 ms32.0050,78430.0 s
Sustained decode16K64Valid2,590.241.0618 ms24.4 ms64.0077,69630.0 s
Sustained decode16K128Over capacity————————
Sustained decode32K1Valid181.5182.167 ms5.5 ms1.015,44430.0 s
Sustained decode32K2Valid286.0143.675 ms7.0 ms2.028,57830.0 s
Sustained decode32K4Valid489.6125.176 ms8.0 ms4.0414,68830.0 s
Sustained decode32K8Valid723.590.8207 ms11.0 ms8.0021,70530.0 s
Sustained decode32K16Valid1,054.566.4359 ms15.1 ms16.0031,63230.0 s
Sustained decode32K32Valid1,455.546.0631 ms21.8 ms32.0043,64830.0 s
Sustained decode32K64Over capacity————————
Sustained decode32K128Over capacity————————
Sustained decode64K1Valid166.9167.9124 ms6.0 ms1.015,00630.0 s
Sustained decode64K2Valid266.8135.1144 ms7.4 ms2.028,00430.0 s
Sustained decode64K4Valid459.5115.0228 ms8.7 ms4.0013,78430.0 s
Sustained decode64K8Valid632.379.4382 ms12.6 ms8.0018,96830.0 s
Sustained decode64K16Valid874.455.0673 ms18.2 ms16.0026,22430.0 s
Sustained decode64K32Over capacity————————
Sustained decode64K64Over capacity————————
Sustained decode64K128Over capacity————————
Sustained decode128K1Valid143.1144.9245 ms6.9 ms1.014,29330.0 s
Sustained decode128K2Valid239.8120.4343 ms8.3 ms2.027,16629.9 s
Sustained decode128K4Valid394.799.0480 ms10.1 ms4.0011,84030.0 s
Sustained decode128K8Valid505.663.5812 ms15.8 ms8.0015,16830.0 s
Sustained decode128K16Over capacity————————
Sustained decode128K32Over capacity————————
Sustained decode128K64Over capacity————————
Sustained decode128K128Over capacity————————
Sustained decode251K1Valid113.3113.6561 ms8.8 ms1.003,39930.0 s
Sustained decode251K2Valid197.298.9754 ms10.1 ms2.005,91630.0 s
Sustained decode251K4Valid316.779.41,164 ms12.6 ms4.009,49230.0 s
Sustained decode251K8Over capacity————————
Sustained decode251K16Over capacity————————
Sustained decode251K32Over capacity————————
Sustained decode251K64Over capacity————————
Sustained decode251K128Over capacity————————

Looped: the model kept repeating the same text, so the benchmark discarded this measurement. Over capacity: not run because this many requests at this context would exceed the server's KV cache.