VOOZH about

URL: https://willitrunai.com/can-run/codestral-22b-on-m1-ultra-128gb


Can Codestral 22B run on Mac Studio M1 Ultra 128GB?

YES — Runs Great

B56Good
Estimated from fit model

Codestral 22B needs ~30.6 GB VRAM. Mac Studio M1 Ultra 128GB has 92.2 GB. With Q4_K_M quantization, expect ~35 tok/s.

Runtime: llama.cppCapacity: RoomyBandwidth: HighStack: 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) — 30.6 GB, 35.2 tok/s, Runs well
30.6 GB required92.2 GB available
33% VRAM used

Fit status

Runs well

Decode

35.2 tok/s

TTFT

5493 ms

Safe context

33K

Memory

30.6 GB / 92.2 GB

Memory breakdown

Weights13.4 GB
KV Cache2.4 GB
Runtime0.9 GB
Headroom13.8 GB

See how fast it feels

See how fast it feelsCodestral 22B on Mac Studio M1 Ultra 128GB
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: 35.2 tok/s decode · 5.5s TTFT (warm) · 88 tok/s prefill

What limits this setup

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.

Best improvement path

Performance by workload

WorkloadGradeFitDecodeTTFTContext
ChatBRuns well35.2 tok/s2996 ms33K
CodingBRuns well35.2 tok/s5493 ms33K
Agentic CodingBRuns well35.2 tok/s7990 ms33K
ReasoningBRuns well35.2 tok/s6492 ms33K
RAGBRuns well35.2 tok/s9987 ms33K

Quantization options

How Codestral 22B (22B params) fits at each quantization level on Mac Studio M1 Ultra 128GB (92.2 GB usable).

QuantBitsVRAMQualityFit
Q2_K
2
8.6 GB
LowC50
Q3_K_S
3
10.8 GB
LowC50
NVFP4
4

Get started

Copy-paste commands to run Codestral 22B on your machine.

Run

ollama run codestral

Upgrade options

Hardware that runs Codestral 22B well

👁 NVIDIA
RTX PRO 6000 Blackwell Workstation Edition 96GBBudget pick
1792 GB/s (+992)
B
Raises estimated decode speed by about 226%.114.6 tok/s decode

Raises estimated decode speed by about 226%.

~$9,999 MSRP

👁 NVIDIA
RTX PRO 6000 Blackwell Server Edition 96GBBest value
1597 GB/s (+797)
B
Raises estimated decode speed by about 190%.102.1 tok/s decode

Raises estimated decode speed by about 190%.

~$9,999 MSRP

Frequently asked questions

See all results for Mac Studio M1 Ultra 128GBSee all hardware for Codestral 22B
12.3 GB
Medium
C50
Q4_K_M
4
13.4 GB
MediumC50
Q5_K_M
5
15.8 GB
HighC50
Q6_K
6
18.0 GB
HighC51
Q8_0
8
23.5 GB
Very HighC51
F16Best for your GPU
16
45.1 GB
MaximumB56

Not always. Mac Studio M1 Ultra 128GB 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.