Can the Apple M1 (8 GB) run CodeGeeX4 All 9B?

Yes, it runs well (tight fit)

Runs well (tight fit). At Q2_K it needs about 5.1 GB of 5.4 GB usable, with an estimated speed of 12.6 tok/s.

Best quant: Q2_K
Generation speed: 12.6 tok/s
Prompt processing: 171 tok/s
First token (1K prompt): 6.0 s
Largest safe context: 13K

Best app to run it on the Apple M1 (8 GB)

On macOS

Command line + local API · runs on llama.cpp (ggml), MLX (Apple silicon, preview)

One command with Ollama’s own build of this model.
Serves an OpenAI-compatible API that other apps and coding tools can use.

ollama run codegeex4:9b-all-q2_K

LM Studio Point-and-click: search, download and chat in one window.
llama.cpp Usually the first to support new model architectures.

Want an agent? CodeGeeX4 All 9B supports tool use, so you can pair a llama.cpp or MLX LM server with one of these. Apps that run on this computer come first.

Coding agents

Personal assistants

How we choose: the files published for this model, your operating system and GPU, whether it fits fully in memory, and published speed tests (MLX vs llama.cpp on Apple silicon, vLLM vs llama.cpp vs Ollama on NVIDIA). Details.

Download CodeGeeX4 All 9B

Recommended for the Apple M1 (8 GB): Q2_K. Every other quantization has its own download link in the table below.

Quickest · Ollama

One command downloads a ready-to-run version and starts a chat.

Get Ollama at ollama.com/download (opens in a new tab) · model page (opens in a new tab)

ollama run codegeex4:9b-all-q2_K

Quantized files · GGUF

Works in LM Studio, llama.cpp, Jan and Ollama. No sign-in needed.

Download the Q2_K (IQ2_M) file (opens in a new tab)

huggingface.co/zai-org/codegeex4-all-9b-GGUF (opens in a new tab)

ollama run hf.co/zai-org/codegeex4-all-9b-GGUF:IQ2_M

Original weights · Hugging Face

Full-precision files from Zhipu AI, for fine-tuning, vLLM, Transformers.

huggingface.co/zai-org/codegeex4-all-9b (opens in a new tab)

No sign-in needed.

Links checked 2 days ago against Hugging Face, Ollama and GitHub.

How it’s rated

Quality 32Basic quality (D) · 32 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 61/100 (quality, fit, speed and memory use) sets the ranking.: How capable the model itself is at Q2_K, from its editorial quality tier scaled by the quantization or precision. It’s the same on any hardware that runs this variant. Scale: A+ 85+ · A 70+ · B 55+ · C 40+ · D under 40.
Runs Runs welltight fit: How well it runs on the Apple M1 (8 GB): speed, capped by how well it fits in memory. Runs great: 30+ tokens/s (or near the image, video or decision speed target) · Runs well: 10+ tokens/s · Slow: 3+ tokens/s · Very slow: under 3 · Won’t run: doesn’t fit even with offload. A tight fit or RAM offload caps it at Runs well; heavy offload caps it at Slow.

Match score

To order lists, each result also gets a match score out of 100 from four parts. It favors the most capable model that still runs well.

Model qualityEditorial quality tier of the model, scaled by the quantization or precision used.	14.5 / 45
Memory fitFull marks when the model fits in the share of unified memory the GPU can use; fewer when it goes past that limit.	24.0 / 25
SpeedGeneration speed against a 40 tokens/s target for LLMs, or render time against a target for image and video.	8.4 / 15
Memory useRewards using the memory you have, so a bigger, better variant beats a tiny one that leaves most memory idle.	15.0 / 15
Match score	61.9 / 100

The match score orders results; it is not shown as a grade. Quality and Runs are the two ratings in the tables.

Every quantization on the Apple M1 (8 GB)

Quant	Memory needed	Available	Speed	Runs	Quality	Download
`Q2_K`	5.1 GB	5.4 GB	12.6 tok/s	Runs welltight fit	32Basic quality (D) · 32 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 61/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (IQ2_M) (opens in a new tab)
`Q3_K_M`	6.0 GB	5.4 GB	8.4 tok/s	Slowfar over GPU memory limit	38Basic quality (D) · 38 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 43/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (IQ3_M) (opens in a new tab)
`Q4_K_M`	7.1 GB	5.4 GB	—	Won't run	43Fair quality (C) · 43 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 5/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q5_K_M`	8.0 GB	5.4 GB	—	Won't run	44Fair quality (C) · 44 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 6/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q6_K`	9.1 GB	5.4 GB	—	Won't run	45Fair quality (C) · 45 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 6/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (Q6_K_L) (opens in a new tab)
`Q8_0`	11.3 GB	5.4 GB	—	Won't run	46Fair quality (C) · 46 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 6/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`F16`	20.2 GB	5.4 GB	—	Won't run	46Fair quality (C) · 46 of 100: how capable the model is at F16, whatever it runs on. Match score 6/100 (quality, fit, speed and memory use) sets the ranking.	Original weights (opens in a new tab)

Memory figures assume 8K of context. Longer conversations or documents grow the KV cache.

Other hardware that runs it

46Fair quality (C) · 46 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 75/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 4070 Ti SUPER Q8_0 · 44.7 tok/s · Runs great
46Fair quality (C) · 46 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 75/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 4080 SUPER Q8_0 · 48.9 tok/s · Runs great
46Fair quality (C) · 46 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 75/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 5070 Ti Q8_0 · 59.6 tok/s · Runs great
46Fair quality (C) · 46 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 75/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 5080 Q8_0 · 63.8 tok/s · Runs great
46Fair quality (C) · 46 of 100: how capable the model is at F16, whatever it runs on. Match score 75/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 5090 F16 · 54.9 tok/s · Runs great
45Fair quality (C) · 45 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 75/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 4070 SUPER Q6_K · 45.7 tok/s · Runs great

Quick answers

How much memory does CodeGeeX4 All 9B need on the M1 8GB?

At Q2_K it needs about 5.1 GB. The M1 8GB has 5.4 GB usable.

How fast is CodeGeeX4 All 9B on the M1 8GB?

About 12.6 tok/s at Q2_K, an estimate from the hardware’s memory bandwidth and the size of the model.

Which quantization of CodeGeeX4 All 9B should I use on the M1 8GB?

Q2_K. Of the versions that fit, it is the one that runs best; when two run equally well, the check prefers the higher-rated one.

Estimates come from published hardware specs and our open formulas, not from running the model on your machine. Real speed varies with runtime, drivers and settings. Numbers marked “Measured” come from a linked benchmark.