RTX 5090 32GBコスパ重視1792 GB/s (+1382)
C
Raises estimated decode speed by about 352%.136.4 tok/sデコード
Raises estimated decode speed by about 352%.
Adds memory headroom for longer context windows and future model growth.
〜$1,999 MSRP
Can GGUF SOLARized GraniStral 14B 1902 YeAM HCT run on MacBook Pro M4 Max 36GB?
YES — Runs Great
C50Usable
Estimated from fit model
GGUF SOLARized GraniStral 14B 1902 YeAM HCT needs ~15.0 GB VRAM. MacBook Pro M4 Max 36GB has 25.9 GB. With Q4_K_M quantization, expect ~30 tok/s.
Runtime: llama.cppCapacity: RoomyBandwidth: LowStack: StandardBottleneck: Balanced
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.
Select quantization to explore
Q4_K_M (Medium quality) — 15.0 GB, 30.2 tok/s, Runs well
15.0 GB required25.9 GB available
58% VRAM used
Fit status
Runs well
Decode
30.2 tok/s
TTFT
6401 ms
Safe context
123K
Memory
15.0 GB / 25.9 GB
Memory breakdown
Weights8.5 GB
KV Cache1.6 GB
Runtime0.9 GB
Headroom3.9 GB
See how fast it feels
See how fast it feelsGGUF SOLARized GraniStral 14B 1902 YeAM HCT 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: 30.2 tok/s decode · 6.4s TTFT (warm) · 76 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
| Workload | Grade | Fit | Decode | TTFT | Context |
|---|---|---|---|---|---|
| Chat | C | Runs well | 30.2 tok/s | 3491 ms | 123K |
| Coding | C | Runs well | 30.2 tok/s | 6401 ms | 123K |
| Agentic Coding | C | Runs well | 30.2 tok/s | 9310 ms | 123K |
| Reasoning | C | Runs well | 30.2 tok/s | 7565 ms | 123K |
| RAG | C | Runs well | 30.2 tok/s | 11638 ms | 123K |
Quantization options
How GGUF SOLARized GraniStral 14B 1902 YeAM HCT (14B params) fits at each quantization level on MacBook Pro M4 Max 36GB (25.9 GB usable).
| Quant | Bits | VRAM | Quality | Fit |
|---|---|---|---|---|
Q2_K | 2 | 5.5 GB | Low | C45 |
Q3_K_S | 3 | 6.9 GB | Low | C46 |
NVFP4 | 4 | 7.8 GB | Medium | C46 |
Q4_K_M | 4 | 8.5 GB | Medium | C46 |
Q5_K_M | 5 | 10.1 GB | High | C47 |
Q6_K | 6 | 11.5 GB | High | C48 |
Q8_0Best for your GPU | 8 | 15.0 GB | Very High | C50 |
F16 | 16 | 28.7 GB | Maximum | F0 |
Get started
Copy-paste commands to run GGUF SOLARized GraniStral 14B 1902 YeAM HCT on your machine.
Run
lms load hf-srs6901--gguf-solarized-granistral-14b-1902-yeam-hct && lms server startアップグレードオプション
GGUF SOLARized GraniStral 14B 1902 YeAM HCTを快適に動かすハードウェア
Frequently asked questions
Can MacBook Pro M4 Max 36GB run GGUF SOLARized GraniStral 14B 1902 YeAM HCT?
Yes, MacBook Pro M4 Max 36GB can run GGUF SOLARized GraniStral 14B 1902 YeAM HCT with a C grade (Runs well). Expected decode speed: 30.2 tok/s.
How much VRAM does GGUF SOLARized GraniStral 14B 1902 YeAM HCT need?
GGUF SOLARized GraniStral 14B 1902 YeAM HCT (14B parameters) requires approximately 15.0 GB of memory with Q4_K_M quantization.
What is the best quantization for GGUF SOLARized GraniStral 14B 1902 YeAM HCT?
The recommended quantization for GGUF SOLARized GraniStral 14B 1902 YeAM HCT is Q4_K_M, which balances quality and memory efficiency.
What speed will GGUF SOLARized GraniStral 14B 1902 YeAM HCT run at on MacBook Pro M4 Max 36GB?
On MacBook Pro M4 Max 36GB, GGUF SOLARized GraniStral 14B 1902 YeAM HCT achieves approximately 30.2 tokens per second decode speed with a time-to-first-token of 6401ms using Q4_K_M quantization.
Can MacBook Pro M4 Max 36GB run GGUF SOLARized GraniStral 14B 1902 YeAM HCT for coding?
For coding workloads, GGUF SOLARized GraniStral 14B 1902 YeAM HCT on MacBook Pro M4 Max 36GB receives a C grade with 30.2 tok/s and 123K context.
What context window can GGUF SOLARized GraniStral 14B 1902 YeAM HCT use on MacBook Pro M4 Max 36GB?
On MacBook Pro M4 Max 36GB, GGUF SOLARized GraniStral 14B 1902 YeAM HCT can safely use up to 123K 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 GGUF SOLARized GraniStral 14B 1902 YeAM HCT?
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.
Embed this result▼
Paste this snippet into any page to show a live fit card.
<iframe src="https://willitrunai.com/embed/hf-srs6901--gguf-solarized-granistral-14b-1902-yeam-hct-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: