VOOZH about

URL: https://willitrunai.com/can-run/codegeex-4-9b-on-arc-b570-10gb


Can CodeGeeX 4 9B run on Intel Arc B570 10GB?

YES — Runs Great

A82Great
Estimated from fit model

CodeGeeX 4 9B needs ~8.0 GB VRAM. Intel Arc B570 10GB has 10.0 GB. With Q4_K_M quantization, expect ~41 tok/s.

Runtime: llama.cppCapacity: RoomyBandwidth: LowStack: StandardBottleneck: Balanced
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) — 8.0 GB, 40.9 tok/s, Runs well
8.0 GB required10.0 GB available
80% VRAM used

Fit status

Runs well

Decode

40.9 tok/s

TTFT

4736 ms

Safe context

68K

Memory

8.0 GB / 10.0 GB

Memory breakdown

Weights5.5 GB
KV Cache0.6 GB
Runtime0.9 GB
Headroom1.0 GB

See how fast it feels

See how fast it feelsCodeGeeX 4 9B on Intel Arc B570 10GB
1st promptCold start — includes initialization
>Write a Python function to sort a list
Here's a Python function that sorts a list using quicksort: def quicksort(arr): if len(arr) <= 1: return arr pivot = arr[len(arr) // 2] left = [x for x in arr if x < pivot] middle = [x for x in arr if x == pivot] right = [x for x in arr if x > pivot] return quicksort(left) + middle + quicksort(right) # Example usage numbers = [3, 6, 8, 10, 1, 2, 1] print(quicksort(numbers)) # [1, 1, 2, 3, 6, 8, 10] The algorithm picks a pivot, partitions the list into smaller, equal, and larger elements, then recursively sorts each partition and concatenates the results.
2nd promptWarm — model ready, no init overhead
>Now add type hints and a docstring
def quicksort(arr: list[int]) -> list[int]: """Sort a list using the quicksort algorithm. Args: arr: List of integers to sort. Returns: A new sorted list. """ if len(arr) <= 1: return arr pivot = arr[len(arr) // 2] left = [x for x in arr if x < pivot] middle = [x for x in arr if x == pivot] right = [x for x in arr if x > pivot] return quicksort(left) + middle + quicksort(right) Added type hints for the input and return type, plus a Google-style docstring.
Estimated: 40.9 tok/s decode · 4.7s TTFT (warm) · 102 tok/s prefill

What limits this setup

The raw memory story may look fine, but the software ecosystem is still a constraint here.

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

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
ChatARuns well40.9 tok/s2583 ms68K
CodingARuns well40.9 tok/s4736 ms68K
Agentic CodingATight fit40.9 tok/s6888 ms68K
ReasoningARuns well37.4 tok/s6121 ms68K
RAGATight fit40.9 tok/s8610 ms68K

Quantization options

How CodeGeeX 4 9B (9B params) fits at each quantization level on Intel Arc B570 10GB (10.0 GB usable).

QuantBitsVRAMQualityFit
Q2_K
2
3.5 GB
LowA80
Q3_K_S
3
4.4 GB
LowA81
NVFP4
4

Get started

Copy-paste commands to run CodeGeeX 4 9B on your machine.

Run

docker run --rm -it ghcr.io/ggerganov/llama.cpp:full \ --hf-repo "THUDM/codegeex4-all-9b" \ --hf-file "codegeex4-all-9b-Q4_K_M.gguf" \ -c 4096 -ngl 99

Frequently asked questions

See all results for Intel Arc B570 10GBSee all hardware for CodeGeeX 4 9B
5.0 GB
Medium
A81
Q4_K_M
4
5.5 GB
MediumA80
Q5_K_MBest for your GPU
5
6.5 GB
HighA80
Q6_K
6
7.4 GB
HighF0
Q8_0
8
9.6 GB
Very HighF0
F16
16
18.5 GB
MaximumF0

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.