VOOZH about

URL: https://willitrunai.com/can-run/wizardlm-13b-on-arc-b570-10gb


Can WizardLM 13B run on Intel Arc B570 10GB?

NO — Won't Fit

F0Won't run
Estimated from fit model

WizardLM 13B needs ~22.0 GB but Intel Arc B570 10GB only has 10.0 GB. Try a smaller quantization or lighter model.

Runtime: llama.cppCapacity: No fitBandwidth: LowStack: StandardBottleneck: Memory capacity
Share:

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) — 22.0 GB, exceeds 10.0 GB available
22.0 GB required10.0 GB available
220% VRAM needed

12.0 GB over capacity — needs offload or smaller quantization

Fit status

Too heavy

Decode

3.9 tok/s

TTFT

49039 ms

Safe context

4K

Memory

22.0 GB / 10.0 GB

Offload

50%

Memory breakdown

Weights7.9 GB
KV Cache12.2 GB
Runtime0.9 GB
Headroom1.0 GB

See how fast it feels

With memory offload — actual speed may be lower
See how fast it feelsWizardLM 13B on Intel Arc B570 10GB
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: 3.9 tok/s decode · 49.0s TTFT (warm) · 10 tok/s prefill

What limits this setup

Usable VRAM is the main blocker for this model.

Not enough usable memory

The model needs 22.0 GB, but this setup only exposes 10.0 GB of usable VRAM.

Runtime ecosystem is narrower than CUDA

Intel GPUs can look attractive on memory per dollar, but local AI tooling, kernels, and model coverage are still broader and easier on CUDA today.

Best improvement path

Add more VRAM headroom

The first useful upgrade is more dedicated VRAM so you can fit the model without shrinking context or dropping to a much lower quant.

Prefer CUDA if you want the path of least resistance

If your goal is maximum runtime coverage, easier troubleshooting, and better support for new local AI releases, CUDA is usually still the safer upgrade path.

Performance by workload

WorkloadGradeFitDecodeTTFTContext
ChatFToo heavy7.7 tok/s13803 ms4K
CodingFToo heavy3.9 tok/s49039 ms4K
Agentic CodingFToo heavy3.9 tok/s72550 ms4K
ReasoningFToo heavy3.9 tok/s57955 ms4K
RAGFToo heavy3.9 tok/s90687 ms4K

Quantization options

How WizardLM 13B (13B params) fits at each quantization level on Intel Arc B570 10GB (10.0 GB usable).

QuantBitsVRAMQualityFit
Q2_K
2
5.1 GB
LowA73
Q3_K_SBest for your GPU
3
6.4 GB
LowA73

Upgrade options

Hardware that runs WizardLM 13B well

👁 Intel
Intel Arc Pro B60 24GBBudget pick
24 GB VRAM (+14)456 GB/s (+76)
A
Makes the model fit on the accelerator instead of staying completely out of reach.31.1 tok/s decode

Makes the model fit on the accelerator instead of staying completely out of reach.

Removes host-memory offload, which is usually the single biggest latency and throughput win.

~$599 MSRP

👁 NVIDIA
RTX 5090 32GBBiggest leap
32 GB VRAM (+22)1792 GB/s (+1412)
A
Makes the model fit on the accelerator instead of staying completely out of reach.146.9 tok/s decode

Makes the model fit on the accelerator instead of staying completely out of reach.

Removes host-memory offload, which is usually the single biggest latency and throughput win.

~$1,999 MSRP

👁 Intel
Intel Data Center GPU Max 1550 128GBBest value
128 GB VRAM (+118)3200 GB/s (+2820)
B
Makes the model fit on the accelerator instead of staying completely out of reach.182 tok/s decode

Makes the model fit on the accelerator instead of staying completely out of reach.

Removes host-memory offload, which is usually the single biggest latency and throughput win.

~$15,000 MSRP

👁 Intel
Gaudi 3 128GBIntel upgrade
128 GB VRAM (+118)3700 GB/s (+3320)
B
Makes the model fit on the accelerator instead of staying completely out of reach.182 tok/s decode

Makes the model fit on the accelerator instead of staying completely out of reach.

Removes host-memory offload, which is usually the single biggest latency and throughput win.

~$15,000 MSRP

Frequently asked questions

See all results for Intel Arc B570 10GBSee all hardware for WizardLM 13B
NVFP4
4
7.3 GB
Medium
F0
Q4_K_M
4
7.9 GB
MediumF0
Q5_K_M
5
9.4 GB
HighF0
Q6_K
6
10.7 GB
HighF0
Q8_0
8
13.9 GB
Very HighF0
F16
16
26.7 GB
MaximumF0

Add more VRAM headroom. The first useful upgrade is more dedicated VRAM so you can fit the model without shrinking context or dropping to a much lower quant.