入門指南排行榜Decode calculator模型OrganizationsReportsMatrix runs硬體基準評測市集租用ProAPI文件
語言
Actual Computer — Every computer, one endpoint

Speed test matrix

limite-1b-violetto on H200 NVL 141GB

vllm · 0.26.0 · BF165 contexts (8K–123K) × 8 concurrency levels (1–128) · prefill at 8K, 16K, 32K, 64K, 123K, 128K
by @keennaylmx dev importMeasured

Hardware

Type
Discrete GPU
GPU
H200 NVL
VRAM
141 GB
OS
linux

Engine

Engine
vllm
Version
0.26.0
Quantization
BF16
Backend
cuda
Build
cuda-13.2

Run

Served model
limite-1b-violetto
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_PLUGINS=limite "$HOME/env_h200-paradigma-inc-vllm-v0260/bin/vllm" serve paradigma-inc/limite-1b-violetto --served-model-name limite-1b-violetto --tensor-parallel-size 1 --reasoning-parser deepseek_r1 --max-model-len 131072 --gpu-memory-utilization 0.86 --host 0.0.0.0 --port 8000 --api-key <redacted> --attention-backend FLASH_ATTN

Prefill

prompt tok/s by context length
8K context15.9K515 ms TTFT
16K context31.4K516 ms TTFT
32K context62.3K517 ms TTFT
64K context88.9K723 ms TTFT
123K context69.9K1,768 ms TTFT
128K context67.2K1,913 ms TTFT

Sustained decode

total tok/s · rows are context length, columns are simultaneous requests
Context1248163264128
8KLooped578.776 ms TTFTLoopedLoopedLoopedLoopedLoopedLooped
16KLoopedLoopedLoopedLoopedLoopedLoopedLoopedLooped
32KLoopedLoopedLoopedLoopedLoopedLoopedLoopedLooped
64KLooped527.3243 ms TTFT986.2236 ms TTFTLoopedLoopedLoopedLoopedLooped
123K252.4309 ms TTFT477.2375 ms TTFTLoopedLoopedLoopedLoopedLoopedOver 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
Prefill8K1Valid15.9K—515 ms——1——
Prefill16K1Valid31.4K—516 ms——1——
Prefill32K1Valid62.3K—517 ms——1——
Prefill64K1Valid88.9K—723 ms——1——
Prefill123K1Valid69.9K—1,768 ms——1——
Prefill128K1Valid67.2K—1,913 ms——1——
Sustained decode8K1Looped—————00—
Sustained decode8K2Valid578.7291.176 ms3.4 ms2.0417,36230.0 s
Sustained decode8K4Looped—————00—
Sustained decode8K8Looped—————00—
Sustained decode8K16Looped—————00—
Sustained decode8K32Looped—————00—
Sustained decode8K64Looped—————00—
Sustained decode8K128Looped—————00—
Sustained decode16K1Looped—————00—
Sustained decode16K2Looped—————00—
Sustained decode16K4Looped—————00—
Sustained decode16K8Looped—————00—
Sustained decode16K16Looped—————00—
Sustained decode16K32Looped—————00—
Sustained decode16K64Looped—————00—
Sustained decode16K128Looped—————00—
Sustained decode32K1Looped—————00—
Sustained decode32K2Looped—————00—
Sustained decode32K4Looped—————00—
Sustained decode32K8Looped—————00—
Sustained decode32K16Looped—————00—
Sustained decode32K32Looped—————00—
Sustained decode32K64Looped—————00—
Sustained decode32K128Looped—————00—
Sustained decode64K1Looped—————00—
Sustained decode64K2Valid527.3268.2243 ms3.7 ms2.0415,81830.0 s
Sustained decode64K4Valid986.2250.7236 ms4.0 ms3.9829,59730.0 s
Sustained decode64K8Looped—————00—
Sustained decode64K16Looped—————00—
Sustained decode64K32Looped—————00—
Sustained decode64K64Looped—————00—
Sustained decode64K128Looped—————00—
Sustained decode123K1Valid252.4257.7309 ms3.9 ms1.027,57330.0 s
Sustained decode123K2Valid477.2245.2375 ms4.1 ms2.0414,31630.0 s
Sustained decode123K4Looped—————00—
Sustained decode123K8Looped—————00—
Sustained decode123K16Looped—————00—
Sustained decode123K32Looped—————00—
Sustained decode123K64Looped—————00—
Sustained decode123K128Over 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.