Will It Run AI

Can OpenSafetyLab MD Judge v0 2 internlm2 7b run on MacBook Pro M4 Max 36GB?

YES — Runs Great

C48Usable
Estimated from fit model

OpenSafetyLab MD Judge v0 2 internlm2 7b needs ~9.9 GB VRAM. MacBook Pro M4 Max 36GB has 25.9 GB. With Q4_K_M quantization, expect ~61 tok/s.

Runtime: llama.cppCapacity: RoomyBandwidth: LowStack: 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) — 9.9 GB, 65.9 tok/s, Runs well
9.9 GB required25.9 GB available
38% VRAM used

Fit status

Runs well

Decode

65.9 tok/s

TTFT

2936 ms

Safe context

329K

Memory

9.9 GB / 25.9 GB

Memory breakdown

Weights4.3 GB
KV Cache0.8 GB
Runtime0.9 GB
Headroom3.9 GB

See how fast it feels

See how fast it feelsOpenSafetyLab MD Judge v0 2 internlm2 7b on MacBook Pro M4 Max 36GB
1st promptCold start — includes initialization
>What is local AI inference?
Local AI inference means running an AI language model directly on your own hardware — your laptop, desktop, or server — instead of sending requests to a remote cloud API. When you run inference locally the model weights are loaded into your GPU or unified memory. Each token you generate requires reading those weights from memory, so memory bandwidth is the main bottleneck for decode speed. Key benefits of running locally: - Full privacy: your prompts never leave your machine - No per-token cost or rate limits - Works offline once the model is downloaded - Latency depends only on your hardware
2nd promptWarm — model ready, no init overhead
>How much VRAM do I need?
It depends on the model size and quantization level. A rough rule of thumb: Model size Q4 (4-bit) Q8 (8-bit) FP16 7B params ~4.3 GB ~7.5 GB ~14 GB 13B params ~7.9 GB ~13.9 GB ~26 GB 70B params ~42.7 GB ~74.9 GB ~140 GB Most people use 4-bit quantization (Q4_K_M) which gives 90-95% of full quality at a fraction of the memory. A 24 GB GPU can comfortably run most 7B-13B models.
Estimated: 65.9 tok/s decode · 2.9s TTFT (warm) · 165 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
ChatCRuns well65.9 tok/s1602 ms329K
CodingCRuns well60.5 tok/s3200 ms329K
Agentic CodingCRuns well65.9 tok/s4271 ms329K
ReasoningCRuns well65.9 tok/s3470 ms329K
RAGCRuns well65.9 tok/s5339 ms329K

Quantization options

How OpenSafetyLab MD Judge v0 2 internlm2 7b (7B params) fits at each quantization level on MacBook Pro M4 Max 36GB (25.9 GB usable).

QuantBitsVRAMQualityFit
Q2_K
2
2.7 GB
LowC43
Q3_K_S
3
3.4 GB
LowC44
NVFP4
4
3.9 GB
MediumC44
Q4_K_M
4
4.3 GB
MediumC44
Q5_K_M
5
5.0 GB
HighC44
Q6_K
6
5.7 GB
HighC45
Q8_0
8
7.5 GB
Very HighC46
F16Best for your GPU
16
14.3 GB
MaximumC50

Get started

Copy-paste commands to run OpenSafetyLab MD Judge v0 2 internlm2 7b on your machine.

Run

lms load hf-richarderkhov--opensafetylab---md-judge-v0-2-internlm2-7b-gguf && lms server start

Frequently asked questions

Can MacBook Pro M4 Max 36GB run OpenSafetyLab MD Judge v0 2 internlm2 7b?

Yes, MacBook Pro M4 Max 36GB can run OpenSafetyLab MD Judge v0 2 internlm2 7b with a C grade (Runs well). Expected decode speed: 60.5 tok/s.

How much VRAM does OpenSafetyLab MD Judge v0 2 internlm2 7b need?

OpenSafetyLab MD Judge v0 2 internlm2 7b (7B parameters) requires approximately 9.9 GB of memory with Q4_K_M quantization.

What is the best quantization for OpenSafetyLab MD Judge v0 2 internlm2 7b?

The recommended quantization for OpenSafetyLab MD Judge v0 2 internlm2 7b is Q4_K_M, which balances quality and memory efficiency.

What speed will OpenSafetyLab MD Judge v0 2 internlm2 7b run at on MacBook Pro M4 Max 36GB?

On MacBook Pro M4 Max 36GB, OpenSafetyLab MD Judge v0 2 internlm2 7b achieves approximately 60.5 tokens per second decode speed with a time-to-first-token of 3200ms using Q4_K_M quantization.

Can MacBook Pro M4 Max 36GB run OpenSafetyLab MD Judge v0 2 internlm2 7b for coding?

For coding workloads, OpenSafetyLab MD Judge v0 2 internlm2 7b on MacBook Pro M4 Max 36GB receives a C grade with 60.5 tok/s and 329K context.

What context window can OpenSafetyLab MD Judge v0 2 internlm2 7b use on MacBook Pro M4 Max 36GB?

On MacBook Pro M4 Max 36GB, OpenSafetyLab MD Judge v0 2 internlm2 7b can safely use up to 329K tokens of context. The model's official context limit is —, but available memory constrains the safe maximum.

Is unified memory on MacBook Pro M4 Max 36GB as fast as VRAM for OpenSafetyLab MD Judge v0 2 internlm2 7b?

Not always. MacBook Pro M4 Max 36GB 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 M4 Max 36GBSee all hardware for OpenSafetyLab MD Judge v0 2 internlm2 7b
Embed this result▼

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

<iframe src="https://willitrunai.com/embed/hf-richarderkhov--opensafetylab---md-judge-v0-2-internlm2-7b-gguf-on-m4-max-36gb" width="400" height="180" frameborder="0" style="border:none;border-radius:12px;overflow:hidden;" title="Will It Run AI — fit result"></iframe>

Preview: