granite-switch-4.1-30b on local hardware
Estimated comfort for repository coding with Aider on a MacBook Pro M4 Pro 48GB.
granite-switch-4.1-30bOpen source
ibm-granite · apache-2.0 · 973 downloads
- Parameters
- 30B exact
- Context window
- 128K tokens
- Attention
- Standard (full attention)
- Layers · KV heads · head dim
- 66 · 8 · 128
- KV cache
- 264 KB/token · 8.3 GB at 32K
- Tool calling
- good (from chat template)
- Thinking
- basic (from chat template)
- Vision
- basic (inferred — no supporting signal)
- Commercial use
- allowedRetain the required license and attribution notices
- Import confidence
- medium · capabilities estimated
Weights by quantization
Q3_K_M
14 GB
computed · low confidence
Q4_K_M
17 GB
computed · low confidence
Q5_K_M
20 GB
computed · low confidence
Q6_K
23 GB
computed · low confidence
Q8_0
30 GB
computed · low confidence
F16 / BF16
56 GB
safetensors file size
- • Assumes GGUF / MLX conversions of this model exist (they do for most popular models). Sizes are computed from bits per weight.
- • vision: basic, inferred from missing signals (low confidence).
- • Capability ratings are estimated from model size and name — this model hasn't been assessed by hand.
granite-switch-4.1-30b — 5-bit
Borderline for your workload
Speed
7–9 tok/s
Too slow
Memory left
7.5 GB
of 48 GB
First word in
≈3 min
Too slow
All the details
- Your setup
- MacBook Pro M4 Pro 48 GB
- Workload
- Repository coding with Aider
- Runtime → tool
- LM Studio → Aider
- Memory used
- 29 GB
- Context
- 32K · up to 4K practical
- Tool support
- Official
- Use-case fit
- Suited
Why?
- Model fits with approximately 7.5 GB of memory headroom.
- LM Studio supports hardware acceleration on this machine (Metal (Apple GPU)).
- Aider can connect to LM Studio (officially supported).
- 32K window; generation drops to 6–8 tok/s when it is full.
- Coding capability is below what interactive coding ideally needs — expect more mistakes or retries.
- Generation (7–9 tok/s) is slow for interactive coding.
- Ingesting a prompt of 14K tokens takes ≈3 min and each step ≈2 min; across ~4 calls a task takes ≈12 min.
Why “Borderline” rather than “Acceptable”?
- Prompt processing: Ingesting the first prompt (14K tokens) takes ≈3 min; each of the ~4 follow-up turns takes ≈2 min (≈12 min per task).
- Generation: Expected 7–9 tok/s at ~16K tokens of context. Coding with repository context is comfortable from about 28 tok/s.
- Context: 32K window; generation drops to 6–8 tok/s when it is full.
- Workload suitability: Coding capability is below what interactive coding ideally needs — expect more mistakes or retries.
How sure are we?
Medium confidenceEstimated from bandwidth and compute, calibrated against 2 verified benchmarks of other models on this same chip (measured with a different engine, so calibration is partial).
- Calibrated with verified benchmarks of other models on this chip.
Medium confidence