CodeGeeX 4 9B needs ~8.7 GB VRAM. MacBook Pro M2 Pro 16GB has 11.5 GB. With Q4_K_M quantization, expect ~28 tok/s.
Operating mode
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.
Select quantization to explore
Fit status
Runs well
Decode
27.9 tok/s
TTFT
6941 ms
Safe context
89K
Memory
8.7 GB / 11.5 GB
This setup is broadly balanced for this model.
Shared-memory contention still exists
The OS, browser, and inference runtime all compete for the same physical memory pool, so real-world headroom is less forgiving than raw capacity suggests.
| Workload | Grade | Fit | Decode | TTFT | Context |
|---|---|---|---|---|---|
| Chat | A | Runs well | 27.9 tok/s | 3786 ms | 89K |
| Coding | A | Runs well | 27.9 tok/s | 6941 ms | 89K |
| Agentic Coding | A | Runs well | 27.9 tok/s | 10096 ms | 89K |
| Reasoning | A | Runs well | 27.9 tok/s | 8203 ms | 89K |
| RAG | A | Runs well | 27.9 tok/s | 12620 ms | 89K |
Inference speed
Estimated decode speed (tokens/sec) for CodeGeeX 4 9B at Q4_K_M across popular GPUs and Apple Silicon, using the fastest local runtime per device. Fastest is RTX 5090 32GB at ~126 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? |
|---|---|---|---|---|
| 32 GB | Q4_K_M | 126.0 | Fits | |
| 24 GB | Q4_K_M | 126.0 | Fits | |
| 24 GB | Q4_K_M | 126.0 | Fits | |
RX 7900 XTX 24GB | 24 GB | Q4_K_M | 126.0 | Fits |
| 16 GB | Q4_K_M | 121.7 | Fits | |
Mac Studio M3 Ultra 256GB | 256 GB | Q4_K_M | 111.0 | Fits |
Mac Studio M2 Ultra 128GB | 128 GB | Q4_K_M | 92.4 | Fits |
Mac Studio M1 Ultra 128GB | 128 GB | Q4_K_M | 87.7 | Fits |
| 12 GB | Q4_K_M | 75.3 | Fits | |
MacBook Pro M4 Max 128GB | 128 GB | Q4_K_M | 74.7 | Fits |
MacBook Pro M4 Max 64GB | 64 GB | Q4_K_M | 74.7 | Fits |
MacBook Pro M3 Max 64GB | 64 GB | Q4_K_M | 47.8 | Fits |
| 12 GB | Q4_K_M | 47.3 | Fits | |
MacBook Pro M1 Max 64GB | 64 GB | Q4_K_M | 43.8 | Fits |
MacBook Pro M4 Pro 48GB | 48 GB | Q4_K_M | 38.5 | Fits |
| 8 GB | Q4_K_M | 36.4 | Offloads |
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.
How CodeGeeX 4 9B (9B params) fits at each quantization level on MacBook Pro M2 Pro 16GB (11.5 GB usable).
| Quant | Bits | VRAM | Quality | Fit |
|---|---|---|---|---|
Q2_K | 2 | 3.5 GB | Low | A78 |
Q3_K_S | 3 | 4.4 GB | Low | A79 |
NVFP4 | 4 | 5.0 GB | Medium | A80 |
Q4_K_M | 4 | 5.5 GB | Medium | A80 |
Q5_K_M | 5 | 6.5 GB | High | A80 |
Q6_KBest for your GPU | 6 | 7.4 GB | High | A80 |
Q8_0 | 8 | 9.6 GB | Very High | F0 |
F16 | 16 | 18.5 GB | Maximum | F0 |
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 99Your hardware
| Model | Params | Grade | Decode | Capabilities |
|---|---|---|---|---|
| 14B | A | 13.8 tok/s | ||
| 14B | B | 13.7 tok/s |
Yes, MacBook Pro M2 Pro 16GB can run CodeGeeX 4 9B with a A grade (Runs well). Expected decode speed: 27.9 tok/s.
CodeGeeX 4 9B (9B parameters) requires approximately 8.7 GB of memory with Q4_K_M quantization.
The recommended quantization for CodeGeeX 4 9B is Q4_K_M, which balances quality and memory efficiency.
On MacBook Pro M2 Pro 16GB, CodeGeeX 4 9B achieves approximately 27.9 tokens per second decode speed with a time-to-first-token of 6941ms using Q4_K_M quantization.
For coding workloads, CodeGeeX 4 9B on MacBook Pro M2 Pro 16GB receives a A grade with 27.9 tok/s and 89K context.
On MacBook Pro M2 Pro 16GB, CodeGeeX 4 9B can safely use up to 89K tokens of context. The model's official context limit is 131K, but available memory constrains the safe maximum.
Not always. MacBook Pro M2 Pro 16GB can often fit larger models thanks to unified memory, but a discrete GPU with dedicated high-bandwidth VRAM may still decode faster once the model fits. For this combination, the important distinction is capacity versus sustained throughput.
Paste this snippet into any page to show a live fit card.
<iframe src="https://willitrunai.com/embed/codegeex-4-9b-on-m2-pro-16gb" width="400" height="180" frameborder="0" style="border:none;border-radius:12px;overflow:hidden;" title="Will It Run AI — fit result"></iframe>
Preview: