Can Codestral 2 25.08 run on MacBook Pro M3 24GB?

BARELY — Tight on Memory

B69Good

Estimated from fit model

Codestral 2 25.08 needs ~19.4 GB VRAM. MacBook Pro M3 24GB has 17.3 GB. With Q4_K_M quantization, expect ~4 tok/s.

Runtime: llama.cppCapacity: OffloadBandwidth: Very lowStack: StandardBottleneck: Host offload

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) — 19.4 GB, 4.3 tok/s, Very compromised (needs ~1.4 GB host RAM)

19.4 GB required17.3 GB available

112% VRAM needed

2.1 GB over capacity — needs offload or smaller quantization

Fit status

Very compromised (needs ~1.4 GB host RAM)

Decode

4.3 tok/s

TTFT

45417 ms

Safe context

Memory

19.4 GB / 17.3 GB

Offload

10%

Memory breakdown

Weights13.4 GB

KV Cache2.4 GB

Runtime0.9 GB

Headroom2.6 GB

See how fast it feels

See how fast it feelsCodestral 2 25.08 on MacBook Pro M3 24GB
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: 4.3 tok/s decode · 45.4s TTFT (warm) · 11 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.

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

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 1.4 GB of extra host RAM just for the offloaded portion, before OS and other tools.

Performance by workload

Workload	Grade	Fit	Decode	TTFT	Context
Chat	A	Runs with offload (needs ~0.6 GB host RAM)	4.7 tok/s	22581 ms	4K
Coding	B	Very compromised (needs ~1.4 GB host RAM)	4.3 tok/s	45417 ms	4K
Agentic Coding	F	Too heavy	3.7 tok/s	76791 ms	4K
Reasoning	B	Very compromised (needs ~1.4 GB host RAM)	4.3 tok/s	53674 ms	4K
RAG	F	Too heavy	3.7 tok/s	95989 ms	4K

Inference speed

Codestral 2 25.08 inference speed — tokens per second by GPU & Mac

Estimated decode speed (tokens/sec) for Codestral 2 25.08 at Q4_K_M across popular GPUs and Apple Silicon, using the fastest local runtime per device. Fastest is RTX 5090 32GB at ~96 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?
RTX 5090 32GB	32 GB	Q4_K_M	96.2	Fits
RX 7900 XTX 24GB	24 GB	Q4_K_M	52.0	Fits
Mac Studio M3 Ultra 256GB	256 GB	Q4_K_M	41.9	Fits
RTX 4090 24GB	24 GB	Q4_K_M	41.7	Fits
RTX 3090 24GB	24 GB	Q4_K_M	38.2	Fits
MacBook Pro M4 Max 128GB	128 GB	Q4_K_M	35.2	Fits
MacBook Pro M4 Max 64GB	64 GB	Q4_K_M	35.2	Fits
Mac Studio M2 Ultra 128GB	128 GB	Q4_K_M	34.9	Fits
Mac Studio M1 Ultra 128GB	128 GB	Q4_K_M	33.1	Fits
MacBook Pro M4 Pro 48GB	48 GB	Q4_K_M	22.2	Fits
RTX 4080 Super 16GB	16 GB	Q4_K_M	18.6	Heavy offload
MacBook Pro M3 Max 64GB	64 GB	Q4_K_M	18.1	Fits
MacBook Pro M1 Max 64GB	64 GB	Q4_K_M	16.6	Fits
RTX 4070 12GB	12 GB	Q4_K_M	6.6	Too big
RTX 3060 12GB	12 GB	Q4_K_M	4.4	Too big
RTX 4060 8GB	8 GB	Q4_K_M	2.0	Too big

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.

Quantization options

How Codestral 2 25.08 (22B params) fits at each quantization level on MacBook Pro M3 24GB (17.3 GB usable).

Quant	Bits	VRAM	Quality	Fit
Q2_K	2	8.6 GB	Low	S85
Q3_K_S	3	10.8 GB	Low	S85
NVFP4Best for your GPU	4	12.3 GB	Medium	A85
Q4_K_M	4	13.4 GB	Medium	F0
Q5_K_M	5	15.8 GB	High	F0
Q6_K	6	18.0 GB	High	F0
Q8_0	8	23.5 GB	Very High	F0
F16	16	45.1 GB	Maximum	F0

Get started

Copy-paste commands to run Codestral 2 25.08 on your machine.

Run

lms load codestral-2508 && lms server start

Opciones de mejora

Hardware que ejecuta bien Codestral 2 25.08

MacBook Pro M4 32GBOpción económica

32 GB Unified (+8)120 GB/s (+20)

Elimina el offload a memoria del sistema, que suele ser la mayor mejora individual en latencia y throughput.9.1 tok/s decodificación

Elimina el offload a memoria del sistema, que suele ser la mayor mejora individual en latencia y throughput.

Sube la velocidad estimada de decodificación alrededor de un 112%.

~$799 MSRP

Mac mini M4 32GBMejor relación calidad-precio

32 GB Unified (+8)120 GB/s (+20)

Elimina el offload a memoria del sistema, que suele ser la mayor mejora individual en latencia y throughput.9.1 tok/s decodificación

Elimina el offload a memoria del sistema, que suele ser la mayor mejora individual en latencia y throughput.

Sube la velocidad estimada de decodificación alrededor de un 112%.

~$1,099 MSRP

Mac mini M4 64GBMejora Apple

64 GB Unified (+40)120 GB/s (+20)

Elimina el offload a memoria del sistema, que suele ser la mayor mejora individual en latencia y throughput.9.1 tok/s decodificación

Elimina el offload a memoria del sistema, que suele ser la mayor mejora individual en latencia y throughput.

Sube la velocidad estimada de decodificación alrededor de un 112%.

~$1,099 MSRP

RTX 5090 Laptop 24GBMayor salto

896 GB/s (+796)

Elimina el offload a memoria del sistema, que suele ser la mayor mejora individual en latencia y throughput.53.8 tok/s decodificación

Elimina el offload a memoria del sistema, que suele ser la mayor mejora individual en latencia y throughput.

Sube la velocidad estimada de decodificación alrededor de un 1151%.

Frequently asked questions

Can MacBook Pro M3 24GB run Codestral 2 25.08?

Yes, MacBook Pro M3 24GB can run Codestral 2 25.08 with a B grade (Very compromised (needs ~1.4 GB host RAM)). Expected decode speed: 4.3 tok/s.

How much VRAM does Codestral 2 25.08 need?

Codestral 2 25.08 (22B parameters) requires approximately 19.4 GB of memory with Q4_K_M quantization.

What is the best quantization for Codestral 2 25.08?

The recommended quantization for Codestral 2 25.08 is Q4_K_M, which balances quality and memory efficiency.

What speed will Codestral 2 25.08 run at on MacBook Pro M3 24GB?

On MacBook Pro M3 24GB, Codestral 2 25.08 achieves approximately 4.3 tokens per second decode speed with a time-to-first-token of 45417ms using Q4_K_M quantization.

Can MacBook Pro M3 24GB run Codestral 2 25.08 for coding?

For coding workloads, Codestral 2 25.08 on MacBook Pro M3 24GB receives a B grade with 4.3 tok/s and 4K context.

What context window can Codestral 2 25.08 use on MacBook Pro M3 24GB?

On MacBook Pro M3 24GB, Codestral 2 25.08 can safely use up to 4K tokens of context. The model's official context limit is 256K, but available memory constrains the safe maximum.

What should I upgrade first if Codestral 2 25.08 feels slow on MacBook Pro M3 24GB?

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.

Is unified memory on MacBook Pro M3 24GB as fast as VRAM for Codestral 2 25.08?

Not always. MacBook Pro M3 24GB 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.

See all results for MacBook Pro M3 24GB See all hardware for Codestral 2 25.08

Embed this result▼

Paste this snippet into any page to show a live fit card.

<iframe src="https://willitrunai.com/embed/codestral-2-25.08-on-m3-24gb" width="400" height="180" frameborder="0" style="border:none;border-radius:12px;overflow:hidden;" title="Will It Run AI — fit result"></iframe>

Preview: