r/BlackwellPerformance

▲ 7 r/BlackwellPerformance+1 crossposts

looking for advice on which PRO 6000 to buy

Hello

I have 2 deals lined up for the Pro 6000
one is for a new Max Q edition, the other is for a one month used Workstation Edition
The new on sell for 10.700 USD, the used WS one is 10.400

My current hardware is a regular motherboard with dual 3090s, and I plan to upgrade to a workstation hardware and to keep the 3090s for supportive work or giving models that needs the extra vram a try, since running them with a performance penalty beats not being able to run them at all, and I don’t plan to add another pro 6000 until two years, depending on my financial circumstances

So what is the better choice? I’m debating myself between the raw power and the temperature situation and the cooling and the ability to run one or both of my 3090s, which i undervolt
Btw my work leans heavily on high concurrency since i process a lot of documents and use a lot of agents for RAG and OCR and data processing

reddit.com
u/Asimology — 1 day ago
▲ 351 r/BlackwellPerformance+1 crossposts

Upgraded to 2x RTX Pro 6000

With the dense Qwen 3.5 / 3.6 models, I've been amazed it has become possible to run almost frontier models locally, on prosumer hardware. I ended up switching my 5090 for a pair of 6000 workstation so I could try larger models.

After some pain with vllm and the realization that I don't actually own real Blackwell cards (consumer GPUs don't use the same architecture as datacenter ones), I got it to run DeepSeek V4 Flash at 80-100 tok/s, with full context and some room for KV cache (+4M with L2 cache). It's definitely a step up from the dense Qwen models for the tasks I have tried so far, mostly research, coding. It feels good enough to replace about 80-90% of 5.5/Opus sessions.

Given how cheap inference on Deepseek models is, it is of course not "worth" it, but it still hits different hearing the coil wine of your build as it is spitting a self contained html for the hundredth time. (Or the smoke detector going off because you missed setting the power limit on the GPUs, and the sudden 1.2KW load triggered big voltage drops on the line)

u/priorityfill — 3 days ago

PSA: Turn on ECC memory

I just realized error checking memory is turned off by default with these cards. It cut my random workload crashes down to zero at what appears to be a close to zero performance loss.

man I love this card.

reddit.com
u/ieatdownvotes4food — 8 days ago
▲ 3 r/BlackwellPerformance+1 crossposts

RTX Pro 96GB vs Macbook pro 128GB

$6699 MBP with no expanding option.
$9xxx RTX Pro 6000
After the apple price increase, i guess making a choice is easier now?

u/SnooCalculations1715 — 10 days ago
▲ 21 r/BlackwellPerformance+2 crossposts

DeepSeek-V4-Flash W4A16+FP8 with MTP self-speculation: 85 tok/s @ 524k on 2× RTX PRO 6000 Max-Q

TL;DR: DeepSeek-V4-Flash running at 85.52 tok/s @ 524k ctx and ~111 tok/s @ 128k single-stream on 2× RTX PRO 6000 Max-Q

pasta-paul's DeepSeek-V4-Flash-W4A16-FP8 quant is great, but its MTP head silently gets stripped at load time (HF transformers has it in _keys_to_ignore_on_load_unexpected), so --speculative-config '{"method":"mtp",...}' is a no-op.

Retrofitted the MTP block, ran a GPTQ pass on its routed experts to match the base's W4A16 INT4 group format, and patched vLLM.

Decode goes from 52.85 tok/s (no MTP) → 85.52 tok/s @ 524k 2-stream → ~111 tok/s @ 128k single-stream. 671B total / 32B active, fits on 2× 96 GB.

Model: https://huggingface.co/LordNeel/DeepSeek-V4-Flash-Acti-MTP-W4A16-FP8

Numbers

2× RTX PRO 6000 Blackwell Max-Q (96 GB each, no NVLink, sm_120):

Profile Decode TPS TTFT Δ vs base
pasta-paul base, no MTP, 524k 52.85 91 ms reference
This model, 524k 2-stream 85.52 155 ms +62% (1.62×)
This model, 128k single-stream ~111 ~310 ms +110% (2.10×)

Sanity-check benchmarks (small samples, full data in the model card):

Benchmark n Score
GSM8K (T=0, COT, exact-match) 100 93%
MMLU (mixed subjects) 100 53% (sample dragged by hard subjects; tracks base)
HumanEval (syntactic check, not pass@1 exec) 50 90%

What got quantized how

  • 768 routed-expert tensors (256 experts × {w1, w2, w3}): W4A16 INT4 group=128 sym, GPTQ (Frantar-style with Cholesky H⁻¹). Calibrated with 256 ultrachat_200k prompts × 256 max_tokens captured from the running pasta-paul model — 17,701 MTP forward dumps, 473k tokens.
  • 5 attention projections: FP8_BLOCK (kept upstream's FP8 weights, just renamed scale → weight_scale to match pasta-paul's compressed-tensors convention).
  • Shared experts, e_proj, h_proj, norms, gate, attn_sink: BF16 / FP32.

Max-Q specific fixes:

If you're on the Max-Q workstation cards specifically: you MUST pass --disable-custom-all-reduce.

vLLM's CustomAllreduce uses CUDA P2P (independent of NCCL_P2P_DISABLE), and on PCIe-only Max-Q topology it deadlocks at post-graph eager warmup.

Without the flag the engine hangs at gpu_worker.py:619 with infinite shm_broadcast.py:681 No available shared memory broadcast block warnings. The Server variant has NVLink and does not hit this.

NCCL tuning that drops TTFT from ~155 ms to ~91 ms on Max-Q at zero decode-TPS cost:

NCCL_PROTO=LL NCCL_ALGO=Ring NCCL_MIN_NCHANNELS=8 
NCCL_NTHREADS=512

How to run

Needs the patched vLLM fork. Vanilla doesn't load DSV4-Flash quants. Base workspace at https://github.com/pasta-paul/dsv4-flash-w4a16-fp8.

Apply the MTP patches on top.

vllm serve LordNeel/DeepSeek-V4-Flash-Acti-MTP-W4A16-FP8 \
  --tensor-parallel-size 2 --kv-cache-dtype fp8 --block-size 256 \
  --max-model-len 524288 --max-num-seqs 2 \
  --gpu-memory-utilization 0.93 \
  --tokenizer-mode deepseek_v4 \
  --tool-call-parser deepseek_v4 --enable-auto-tool-choice \
  --reasoning-parser deepseek_v4 \
  --trust-remote-code \
  --disable-custom-all-reduce \
  --speculative-config '{"method":"mtp","num_speculative_tokens":1}' \
  --host 0.0.0.0 --port 8000

I also wrote an AGENTS.md runbook. Point Claude/Codex/Cursor to it and tell it "set this up"/ "verify hardware and get this model running"/ or similar. Goes through preflight → CUDA toolkit (no sudo via conda) → patched vLLM build → download → patches → serve → smoke test.

Limitations

  • TP=2 only. TP=1 OOMs on a single RTX6000 pro; TP≥4 hits an upstream W4A16 MoE scale-sharding bug (vllm-project/vllm#41511).
  • num_speculative_tokens capped at 1. DSV4 flash ships exactly one MTP head (num_nextn_predict_layers=1); higher values will not produce more drafts.
  • Reasoning parser caveat. With --reasoning-parser deepseek_v4, output splits into content and reasoning_content. Clients reading only content see empty strings on "thinking" responses.
  • MTP GPTQ skipped attention during calibration — see Future work in card.
  • Hardware tested: only Max-Q. Server variant + DGX Spark + H200 should work but I have not run them.

Request for the community

If you run this and the MTP draft acceptance rate comes out significantly different on your prompt distribution, please do comment with your domain and the rate (vLLM will log it as spec_decode_acceptance_rate).

Credits

  • DeepSeek-AI for the base model
  • pasta-paul for the W4A16+FP8 quant + jasl/vllm serving stack (repo)

u/Blahblahblakha — 9 days ago
▲ 0 r/BlackwellPerformance+1 crossposts

Its done. not we are so back. It's done, local is frontier REAP 504B 309GB

Update test finished with score 86.2. I'd say its safe to add 3 pts due to me running with lower context window before it became possible to extend it on my setup. We are done. Frontier at home.

https://preview.redd.it/pip3ji3jzy8h1.png?width=1483&format=png&auto=webp&s=065a648ff7719221efbde05819902e1c6d320e0e

started test with 300k context then 400k, then 1M became possible thanks to the boys and girls in the rtx6000pro discord. test is not finished but its safe to say local ai has done it. 309GB. if not for exhausted context windows the score would have gained 2-3 points over what the final will be. please join rtx pro6000 or aider discord for final score and discussion

reddit.com
u/Sorry_Ad191 — 13 days ago