VOOZH about

URL: https://willitrunai.com/can-run/codegeex-4-9b-on-rtx-4050-laptop-6gb


Can CodeGeeX 4 9B run on RTX 4050 Laptop 6GB?

YES — With Q3_K_S

B67Good
Estimated from fit model

CodeGeeX 4 9B needs ~6.8 GB VRAM. RTX 4050 Laptop 6GB has 6.0 GB. With Q3_K_S quantization, expect ~19 tok/s.

Runtime: OllamaCapacity: OffloadBandwidth: Very lowStack: BasicBottleneck: Host offload
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.

CodeGeeX 4 9B at Q4_K_M needs 7.9 GB — too much for RTX 4050 Laptop 6GB (6.0 GB). Runs at Q3_K_S (6.8 GB) with low quality. 2 quantization levels fit.
Capabilities:

Select quantization to explore

Q4_K_M (Medium quality) — 7.9 GB, exceeds 6.0 GB available
7.9 GB required6.0 GB available
132% VRAM needed

1.9 GB over capacity — needs offload or smaller quantization

Fit status

Too heavy

Decode

11.7 tok/s

TTFT

16497 ms

Safe context

4K

Memory

7.9 GB / 6.0 GB

Offload

20%

Memory breakdown

Weights5.5 GB
KV Cache0.6 GB
Runtime1.2 GB
Headroom0.6 GB

See how fast it feels

With memory offload — actual speed may be lower
See how fast it feelsCodeGeeX 4 9B on RTX 4050 Laptop 6GB
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: 11.7 tok/s decode · 16.5s TTFT (warm) · 29 tok/s prefill

What limits this setup

It fits through host-memory offload, and offload is the main reason performance drops.

CPU or host-memory offload is active

About 10% of the working set spills out of accelerator memory, which usually hurts latency and sustained decode throughput.

Very little memory headroom

You can run the model, but there is not much room left for longer context, bigger batches, extra apps, or future model updates.

Best improvement path

Remove offload with more accelerator memory

Prioritize a GPU or unified-memory tier that fits the whole model natively. Removing offload usually helps more than small compute gains.

Buy headroom, not only minimum fit

A slightly larger memory tier gives you safer context growth and makes the recommendation more future-proof.

Increase host RAM if you keep offloading

This setup may need roughly 0.5 GB of extra host RAM just for the offloaded portion, before OS and other tools.

Performance by workload

WorkloadGradeFitDecodeTTFTContext
ChatFToo heavy11.7 tok/s9059 ms4K
CodingFToo heavy11.7 tok/s16497 ms4K
Agentic CodingFToo heavy10.0 tok/s28065 ms4K
ReasoningFToo heavy11.7 tok/s19497 ms4K
RAGFToo heavy10.0 tok/s35082 ms4K

Quantization options

How CodeGeeX 4 9B (9B params) fits at each quantization level on RTX 4050 Laptop 6GB (6.0 GB usable).

QuantBitsVRAMQualityFit
Q2_KBest for your GPU
2
3.5 GB
LowA81
Q3_K_S
3
4.4 GB
LowF0

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

Upgrade options

Hardware that runs CodeGeeX 4 9B well

👁 NVIDIA
RTX 3050 8GBBudget pick
8 GB VRAM (+2)224 GB/s (+32)
A
Makes the model fit on the accelerator instead of staying completely out of reach.21.5 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.

~$249 MSRP

👁 NVIDIA
RTX 5060 8GBBest value
8 GB VRAM (+2)448 GB/s (+256)
A
Makes the model fit on the accelerator instead of staying completely out of reach.40.6 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.

~$299 MSRP

👁 NVIDIA
RTX 4060 8GBNVIDIA upgrade
8 GB VRAM (+2)272 GB/s (+80)
A
Makes the model fit on the accelerator instead of staying completely out of reach.28.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.

~$299 MSRP

👁 NVIDIA
RTX 3080 Ti 12GBBiggest leap
12 GB VRAM (+6)912 GB/s (+720)
A
Makes the model fit on the accelerator instead of staying completely out of reach.126 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,199 MSRP

Frequently asked questions

See all results for RTX 4050 Laptop 6GBSee all hardware for CodeGeeX 4 9B
NVFP4
4
5.0 GB
Medium
F0
Q4_K_M
4
5.5 GB
MediumF0
Q5_K_M
5
6.5 GB
HighF0
Q6_K
6
7.4 GB
HighF0
Q8_0
8
9.6 GB
Very HighF0
F16
16
18.5 GB
MaximumF0

Remove offload with more accelerator memory. Prioritize a GPU or unified-memory tier that fits the whole model natively. Removing offload usually helps more than small compute gains.