Bắt đầuBảng xếp hạngDecode calculatorMô hìnhOrganizationsReportsMatrix runsPhần cứngĐánh giá chuẩnChợCho thuêProTài liệu API
Ngôn ngữ
Actual Computer — Every computer, one endpoint

Speed test matrix

Apex-35B-V1.0 on CMP 170HX 64GB ×2

vllm · 0.32.0rc1.dev249+g18305948a · BF166 contexts (0–248K) × 8 concurrency levels (1–128) · prefill at 8K, 16K, 32K, 64K, 128K
by @Sandbergllm-inference-bench v0.8.0Measured

Hardware

Type
Discrete GPU
GPU
CMP 170HX
GPU count
2
VRAM
64 GB (2 × 32 GB)
CPU
2x Intel Xeon E5-2630 v3
RAM
64 GB
OS
Ubuntu 26.04.1

Engine

Engine
vllm
Version
0.32.0rc1.dev249+g18305948a
Quantization
BF16
Backend
cuda
Build
ghcr.io/morrowmake/vllm-cmp170hx@sha256:5b45c4d6feafefe2eba962375b0a9a0b64fd22b9e05abb4d1966f14a32a2db79

Run

Served model
bench
Revision
5105f8f9ed8fd8212a72da546bcbb4f01d2cfd68
Decode test
Fixed duration
Prefill mode
Measured during decode warm-up
Time per measurement
30 s
Max output
8,192 tokens

Launch command

# Untuned out-of-the-box baseline. Spec decode: none. Layout: PP2 (stock vLLM flag)
# 2x NVIDIA CMP 170HX 64GB (cmpunlocker), 180 W limit, PCIe Gen2 x4 | 2x Intel Xeon E5-2630 v3 | 64 GB DDR4 | Ubuntu 26.04.1, NVIDIA driver 610.57.04 | vLLM: Morrowmake vllm-cmp170hx image
vllm serve Apexintelligence-AI/Apex-35B-V1.0 --revision 5105f8f9ed8fd8212a72da546bcbb4f01d2cfd68 --max-model-len 262144 --gpu-memory-utilization 0.94 --max-num-seqs 128 --enable-prefix-caching --trust-remote-code --pipeline-parallel-size 2 --language-model-only

Prefill

prompt tok/s by context length
8K context11.7K699 ms TTFT
16K context11.2K1,434 ms TTFT
32K context11K2,913 ms TTFT
64K context9,9936,406 ms TTFT
128K context7,67716,658 ms TTFT

Sustained decode

total tok/s · rows are context length, columns are simultaneous requests
Context1248163264128
0126.4134 ms TTFT215.3159 ms TTFT354.4173 ms TTFT493.1303 ms TTFT774.0366 ms TTFT1,133.2467 ms TTFT1,930.6565 ms TTFT2,901.5850 ms TTFT
16K121.7292 ms TTFT208.0347 ms TTFT335.1472 ms TTFT499.8728 ms TTFT674.11,235 ms TTFT1,083.52,202 ms TTFT1,528.14,226 ms TTFTOver capacity
32K116.7389 ms TTFT199.9493 ms TTFT321.2640 ms TTFTLooped622.91,450 ms TTFT956.52,619 ms TTFTOver capacityOver capacity
64K110.3644 ms TTFT189.3714 ms TTFT295.5984 ms TTFT420.21,507 ms TTFT538.22,514 ms TTFT785.44,295 ms TTFTOver capacityOver capacity
128K99.7969 ms TTFT170.91,184 ms TTFTLooped345.82,565 ms TTFT332.74,530 ms TTFTOver capacityOver capacityOver capacity
248K84.91,909 ms TTFT144.92,485 ms TTFT155.43,523 ms TTFT187.25,379 ms TTFTOver 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
Prefill8K1Valid11.7K—699 ms——1——
Prefill16K1Valid11.2K—1,434 ms——1——
Prefill32K1Valid11K—2,913 ms——1——
Prefill64K1Valid9,993.0—6,406 ms——1——
Prefill128K1Valid7,677.0—16,658 ms——1——
Sustained decode01Valid126.4126.5134 ms7.9 ms1.003,79130.0 s
Sustained decode02Valid215.3107.5159 ms9.3 ms2.006,45730.0 s
Sustained decode04Valid354.488.7173 ms11.3 ms4.0010,63130.0 s
Sustained decode08Valid493.161.8303 ms16.2 ms8.0014,79230.0 s
Sustained decode016Valid774.049.5366 ms20.2 ms16.0023,21630.0 s
Sustained decode032Valid1,133.236.3467 ms27.5 ms32.0034,01630.0 s
Sustained decode064Valid1,930.630.9565 ms32.3 ms64.0057,92030.0 s
Sustained decode0128Valid2,901.523.4850 ms42.8 ms128.0087,04030.0 s
Sustained decode16K1Valid121.7121.9292 ms8.2 ms1.003,65130.0 s
Sustained decode16K2Valid208.0104.0347 ms9.6 ms2.006,24130.0 s
Sustained decode16K4Valid335.183.5472 ms12.0 ms4.0010,05230.0 s
Sustained decode16K8Valid499.862.0728 ms16.1 ms8.0014,99230.0 s
Sustained decode16K16Valid674.141.41,235 ms24.2 ms16.0020,22430.0 s
Sustained decode16K32Valid1,083.532.82,202 ms30.5 ms32.0032,51230.0 s
Sustained decode16K64Valid1,528.122.54,226 ms44.5 ms64.0045,85630.0 s
Sustained decode16K128Over capacity————————
Sustained decode32K1Valid116.7116.9389 ms8.6 ms1.003,50030.0 s
Sustained decode32K2Valid199.9100.0493 ms10.0 ms2.005,99630.0 s
Sustained decode32K4Valid321.280.0640 ms12.5 ms4.009,63630.0 s
Sustained decode32K8Looped—————00—
Sustained decode32K16Valid622.938.21,450 ms26.2 ms16.0018,68030.0 s
Sustained decode32K32Valid956.528.82,619 ms34.7 ms32.0028,68830.0 s
Sustained decode32K64Over capacity————————
Sustained decode32K128Over capacity————————
Sustained decode64K1Valid110.3110.7644 ms9.0 ms1.003,30830.0 s
Sustained decode64K2Valid189.394.7714 ms10.6 ms2.005,67930.0 s
Sustained decode64K4Valid295.573.4984 ms13.6 ms4.008,86630.0 s
Sustained decode64K8Valid420.251.51,507 ms19.4 ms8.0012,60430.0 s
Sustained decode64K16Valid538.232.62,514 ms30.7 ms16.0016,14730.0 s
Sustained decode64K32Valid785.422.74,295 ms44.0 ms32.0023,55230.0 s
Sustained decode64K64Over capacity————————
Sustained decode64K128Over capacity————————
Sustained decode128K1Valid99.7100.1969 ms10.0 ms1.002,99130.0 s
Sustained decode128K2Valid170.985.71,184 ms11.7 ms2.005,12730.0 s
Sustained decode128K4Looped—————00—
Sustained decode128K8Valid345.843.02,565 ms23.2 ms8.0010,37230.0 s
Sustained decode128K16Valid332.720.74,530 ms48.2 ms16.009,97930.0 s
Sustained decode128K32Over capacity————————
Sustained decode128K64Over capacity————————
Sustained decode128K128Over capacity————————
Sustained decode248K1Valid84.985.51,909 ms11.7 ms1.002,54630.0 s
Sustained decode248K2Valid144.972.62,485 ms13.8 ms2.004,34730.0 s
Sustained decode248K4Valid155.438.83,523 ms25.8 ms4.004,66030.0 s
Sustained decode248K8Valid187.223.25,379 ms43.2 ms8.005,61630.0 s
Sustained decode248K16Over capacity————————
Sustained decode248K32Over capacity————————
Sustained decode248K64Over capacity————————
Sustained decode248K128Over 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.