Can Qwen 3 32B run on B100 192GB?

YES — Runs Great

S88Excellent

Estimated from fit model

Qwen 3 32B needs ~43.8 GB VRAM. B100 192GB has 192.0 GB. With Q4_K_M quantization, expect ~374 tok/s.

Runtime: OllamaCapacity: RoomyBandwidth: HighStack: BasicBottleneck: Balanced

Operating mode

Choose the run profile you care about

Interactive favors responsiveness, while light API and scale-out lean harder on serving readiness. The fit stays the same, but the recommendation lens changes.

Current mode

Balanced

Balanced for general local use. Keeps the ranking neutral across personal and serving workflows.

Capabilities:

Select quantization to explore

Q4_K_M (Medium quality) — 43.8 GB, 374.4 tok/s, Runs well

43.8 GB required192.0 GB available

23% VRAM used

Fit status

Runs well

Decode

374.4 tok/s

TTFT

517 ms

Safe context

131K

Memory

43.8 GB / 192.0 GB

Memory breakdown

Weights19.5 GB

KV Cache3.9 GB

Runtime1.2 GB

Headroom19.2 GB

See how fast it feels

See how fast it feelsQwen 3 32B on B100 192GB
1st promptCold start — includes initialization
>Solve: If a train travels at 60 mph for 2.5 hours, how far does it go?
Let me work through this step by step.

Given information:
  - Speed = 60 mph (miles per hour)
  - Time  = 2.5 hours

Formula: Distance = Speed x Time

Calculation:
  Distance = 60 mph x 2.5 h
           = 150 miles

The train travels 150 miles.

Double-check: at 60 mph the train covers 60 miles each hour. In half an hour it covers 30 miles. So in 2.5 hours: 60 + 60 + 30 = 150 miles. Confirmed.
2nd promptWarm — model ready, no init overhead
>What if the train stops for 20 minutes halfway?
The stop doesn't change the total distance covered while moving, but it affects total trip time.

Breakdown:
  - First half: 1.25 hours at 60 mph = 75 miles
  - Stop: 20 minutes (no distance)
  - Second half: 1.25 hours at 60 mph = 75 miles

Total distance: 150 miles (same)
Total time: 2.5 h + 0.33 h = 2.83 hours
Average speed: 150 / 2.83 = 53 mph

The distance stays the same but average speed drops to 53 mph because of the stop.
Estimated: 374.4 tok/s decode · 517ms TTFT (warm) · 936 tok/s prefill

What limits this setup

This setup is broadly balanced for this model.

No major red flags

This recommendation has enough memory headroom and acceptable estimated speed for the selected workload.

Best improvement path

Performance by workload

Workload	Grade	Fit	Decode	TTFT	Context
Chat	S	Runs well	374.4 tok/s	350 ms	131K
Coding	S	Runs well	374.4 tok/s	517 ms	131K
Agentic Coding	S	Runs well	374.4 tok/s	752 ms	131K
Reasoning	S	Runs well	374.4 tok/s	611 ms	131K
RAG	S	Runs well	374.4 tok/s	940 ms	131K

Inference speed

Qwen 3 32B inference speed — tokens per second by GPU & Mac

Estimated decode speed (tokens/sec) for Qwen 3 32B at Q4_K_M across popular GPUs and Apple Silicon, using the fastest local runtime per device. Fastest is RTX 5090 32GB at ~67 tok/s. Speed is memory-bandwidth bound, so cards that fit the whole model in VRAM run far faster than ones that offload to system RAM.

GPU / Mac	Memory	Quant	Speed (tok/s)	Fits?
RTX 5090 32GB	32 GB	Q4_K_M	66.9	Tight
MacBook Pro M4 Max 128GB	128 GB	Q4_K_M	33.5	Fits
MacBook Pro M4 Max 64GB	64 GB	Q4_K_M	33.5	Fits
Mac Studio M3 Ultra 256GB	256 GB	Q4_K_M	31.0	Fits
Mac Studio M2 Ultra 128GB	128 GB	Q4_K_M	25.9	Fits
RTX 4090 24GB	24 GB	Q4_K_M	24.9	Heavy offload
Mac Studio M1 Ultra 128GB	128 GB	Q4_K_M	24.5	Fits
RX 7900 XTX 24GB	24 GB	Q4_K_M	23.0	Heavy offload
RTX 3090 24GB	24 GB	Q4_K_M	21.3	Heavy offload
MacBook Pro M4 Pro 48GB	48 GB	Q4_K_M	21.1	Tight
MacBook Pro M3 Max 64GB	64 GB	Q4_K_M	13.4	Fits
MacBook Pro M1 Max 64GB	64 GB	Q4_K_M	12.3	Fits
RTX 4080 Super 16GB	16 GB	Q4_K_M	9.0	Too big
RTX 4070 12GB	12 GB	Q4_K_M	3.2	Too big
RTX 3060 12GB	12 GB	Q4_K_M	2.0	Too big
RTX 4060 8GB	8 GB	Q4_K_M	2.0	Too big

Estimates for single-stream decoding at Q4_K_M; real tokens/sec varies with prompt length, context, batch size, and runtime build. Prompt processing (prefill) is faster than the decode figures shown here.

Quantization options

How Qwen 3 32B (32B params) fits at each quantization level on B100 192GB (192.0 GB usable).

Quant	Bits	VRAM	Quality	Fit
Q2_K	2	12.5 GB	Low	A78
Q3_K_S	3	15.7 GB	Low	A78
NVFP4	4	17.9 GB	Medium	A78
Q4_K_M	4	19.5 GB	Medium	A78
Q5_K_M	5	23.0 GB	High	A79
Q6_K	6	26.2 GB	High	A79
Q8_0	8	34.2 GB	Very High	A80
F16Best for your GPU	16	65.6 GB	Maximum	A84

Get started

Copy-paste commands to run Qwen 3 32B on your machine.

Run

ollama run qwen3:32b

Your hardware

More models your B100 192GB can run

Model	Params	Grade	Decode
Devstral 2 123B Instruct	123B	S	97.4 tok/s
Qwen 3.5 122B A10B	122B	S	270.2 tok/s
DeepSeek V4 Flash	284B	S	144.8 tok/s
Qwen 3.6 35B A3B	35B	S	854 tok/s
Qwen 3.5 35B A3B	35B	S	928.7 tok/s

Frequently asked questions

Can B100 192GB run Qwen 3 32B?

Yes, B100 192GB can run Qwen 3 32B with a S grade (Runs well). Expected decode speed: 374.4 tok/s.

How much VRAM does Qwen 3 32B need?

Qwen 3 32B (32B parameters) requires approximately 43.8 GB of memory with Q4_K_M quantization.

What is the best quantization for Qwen 3 32B?

The recommended quantization for Qwen 3 32B is Q4_K_M, which balances quality and memory efficiency.

What speed will Qwen 3 32B run at on B100 192GB?

On B100 192GB, Qwen 3 32B achieves approximately 374.4 tokens per second decode speed with a time-to-first-token of 517ms using Q4_K_M quantization.

Can B100 192GB run Qwen 3 32B for coding?

For coding workloads, Qwen 3 32B on B100 192GB receives a S grade with 374.4 tok/s and 131K context.

What context window can Qwen 3 32B use on B100 192GB?

On B100 192GB, Qwen 3 32B can safely use up to 131K tokens of context. The model's official context limit is 131K, but available memory constrains the safe maximum.

See all results for B100 192GB See all hardware for Qwen 3 32B

Embed this result▼

Paste this snippet into any page to show a live fit card.

<iframe src="https://willitrunai.com/embed/qwen-3-32b-on-b100-192gb" width="400" height="180" frameborder="0" style="border:none;border-radius:12px;overflow:hidden;" title="Will It Run AI — fit result"></iframe>

Preview: