llamaperf

RTX 6000

NVIDIA · 48GB · 5 reports

See what fits on this GPU →

Use the calculator to check which models fit in 48 GB of VRAM. The reports below include different GPU counts and memory setups; a model listed here may need extra cards or CPU offloading.

How to compare these reports →
Tone: positive
reported speed:
128.6 tokens/s generation

Reported by the source; GPU count, offloading and concurrent requests can change this figure. Check the full setup before comparing.

Running DeepSeek V4 Flash on a single RTX 6000 Pro using vLLM-Moet. Context length set to 130K. Requires ~150GB RAM for loading. Benchmarks show generation speeds around 100-130 t/s.

DeepSeek V4 Flash 284B (13B active)

RTX 6000 · llama.cpp · 250,000 ctx

Tone: positive
reported speed:
27.2 tokens/s generation · 14860.0 tokens/s prompt processing
quant:
Q3_K_XL (GGUF)

Reported by the source; GPU count, offloading and concurrent requests can change this figure. Check the full setup before comparing.

creative-writing

User reports running DeepSeek V4 Flash 0731 with Q3_K_XL quant on dual GPU setup (RTX 6000 96GB + W7800 48GB) using llama.cpp server. Achieved 27.2 t/s generation speed. Mentions it's cheaper than K3 and GLM 5.2 but very good.

Qwen3.8 27B

RTX 6000 · sglang · 262,144 ctx

Tone: mixed
reported speed:
150.0 tokens/s generation
quant:
FP8
kv:
FP8

Reported by the source; GPU count, offloading and concurrent requests can change this figure. Check the full setup before comparing.

agenticlong-context

User runs Qwen 3.8 27B FP8 on two RTX 6000 Pro GPUs with sglang, getting 150 tk/sec but tasks take 12x longer than Claude Opus 5. They also tested BF16 on primary card with FP8 offloading, which took 3 hours vs 1h45m for FP8. Context lengths tested: 256k, 128k (too small), 500k (faster despite unsupported). They use a skill that reads large documentation files, hitting 80k context before starting. They compare against Claude Code, Pi Code, Qwen Code, and Hermes. They are learning and using ChatGPT 5.6 high for testing.

Tone: mixed
reported speed:
40.0 tokens/s generation · 2000.0 tokens/s prompt processing
quant:
IQ4 (gguf)
kv:
Q8

Reported by the source; GPU count, offloading and concurrent requests can change this figure. Check the full setup before comparing.

User reports prefill ~2000 tps and decode ~40 tps for single request; with 2-4 parallel requests, prefill drops to 500-1000 tps and decode to 10-20 tps. They are seeking a better setup for 2-4 slots with q4 quants or better and q8 kv cache or better. They mention trying vLLM recipes before.

Qwen3.8 27B

RTX 6000 · llama.cpp

Tone: positive
reported speed:
140.6 tokens/s generation

Reported by the source; GPU count, offloading and concurrent requests can change this figure. Check the full setup before comparing.

User reports dflash2 speeds up Qwen 3.8 27B up to 4x, with median 140.6 tok/s vs baseline 47.4 tok/s. Caveat: gains vary by task, sometimes only 1.5x. Mentions being from atomic.chat team.