LFM2 24B needs ~31.8 GB VRAM. MacBook Pro M3 Max 128GB has 92.2 GB. With Q4_K_M quantization, expect ~18 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
17.6 tok/s
TTFT
10986 ms
Safe context
131K
Memory
31.8 GB / 92.2 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 | 17.6 tok/s | 5992 ms | 131K |
| Coding | A | Runs well | 17.6 tok/s | 10986 ms | 131K |
| Agentic Coding | A | Runs well | 17.6 tok/s | 15979 ms | 131K |
| Reasoning | A | Runs well | 17.6 tok/s | 12983 ms | 131K |
| RAG | A | Runs well | 17.6 tok/s | 19974 ms | 131K |
Inference speed
Estimated decode speed (tokens/sec) for LFM2 24B at Q4_K_M across popular GPUs and Apple Silicon, using the fastest local runtime per device. Fastest is RTX 5090 32GB at ~88 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 | 88.2 | Fits | |
| 24 GB | Q4_K_M | 56.3 | Tight | |
RX 7900 XTX 24GB | 24 GB | Q4_K_M | 50.8 | Tight |
| 24 GB | Q4_K_M | 48.1 | Tight | |
Mac Studio M3 Ultra 256GB | 256 GB | Q4_K_M | 40.9 | Fits |
MacBook Pro M4 Max 128GB | 128 GB | Q4_K_M | 36.8 | Fits |
MacBook Pro M4 Max 64GB | 64 GB | Q4_K_M | 36.8 | Fits |
Mac Studio M2 Ultra 128GB | 128 GB | Q4_K_M | 34.1 | Fits |
Mac Studio M1 Ultra 128GB | 128 GB | Q4_K_M | 32.3 | Fits |
MacBook Pro M4 Pro 48GB | 48 GB | Q4_K_M | 23.2 | Fits |
| 16 GB | Q4_K_M | 21.3 | Too big | |
MacBook Pro M3 Max 64GB | 64 GB | Q4_K_M | 17.6 | Fits |
MacBook Pro M1 Max 64GB | 64 GB | Q4_K_M | 16.2 | Fits |
| 12 GB | Q4_K_M | 7.5 | Too big | |
| 12 GB | Q4_K_M | 4.7 | Too big | |
| 8 GB | Q4_K_M | 2.2 | 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.
How LFM2 24B (24B params) fits at each quantization level on MacBook Pro M3 Max 128GB (92.2 GB usable).
| Quant | Bits | VRAM | Quality | Fit |
|---|---|---|---|---|
Q2_K | 2 | 9.4 GB | Low | A73 |
Q3_K_S | 3 | 11.8 GB | Low | A73 |
NVFP4 | 4 | 13.4 GB | Medium | A73 |
Q4_K_M | 4 | 14.6 GB | Medium | A73 |
Q5_K_M | 5 | 17.3 GB | High | A74 |
Q6_K | 6 | 19.7 GB | High | A74 |
Q8_0 | 8 | 25.7 GB | Very High | A75 |
F16Best for your GPU | 16 | 49.2 GB | Maximum | A80 |
Copy-paste commands to run LFM2 24B on your machine.
Run
ollama run lfm2Your hardware
| Model | Params | Grade | Decode | Capabilities |
|---|---|---|---|---|
| 123B | S | 3.3 tok/s | ||
| 30.5B | S | 36.3 tok/s | ||
| 27B | S | 15.7 tok/s | ||
| 27B | S | 12 tok/s | ||
| 122B | S | 15 tok/s |
Yes, MacBook Pro M3 Max 128GB can run LFM2 24B with a A grade (Runs well). Expected decode speed: 17.6 tok/s.
LFM2 24B (24B parameters) requires approximately 31.8 GB of memory with Q4_K_M quantization.
The recommended quantization for LFM2 24B is Q4_K_M, which balances quality and memory efficiency.
On MacBook Pro M3 Max 128GB, LFM2 24B achieves approximately 17.6 tokens per second decode speed with a time-to-first-token of 10986ms using Q4_K_M quantization.
For coding workloads, LFM2 24B on MacBook Pro M3 Max 128GB receives a A grade with 17.6 tok/s and 131K context.
On MacBook Pro M3 Max 128GB, LFM2 24B can safely use up to 131K tokens of context. The model's official context limit is 131K, but available memory constrains the safe maximum.
Not always. MacBook Pro M3 Max 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.
Paste this snippet into any page to show a live fit card.
<iframe src="https://willitrunai.com/embed/lfm2-24b-on-m3-max-128gb" width="400" height="180" frameborder="0" style="border:none;border-radius:12px;overflow:hidden;" title="Will It Run AI — fit result"></iframe>
Preview: