Local AI Advisor

MiniCPM-V-4.7-1B on local hardware

Estimated comfort for repository coding with Aider on a MacBook Pro M4 Pro 48GB.

MiniCPM-V-4.7-1BOpen source

openbmb · apache-2.0 · 33,388 downloads

Hugging Face
VisionReasoning / thinking mode
Parameters
1.6B exact
Context window
256K tokens
Attention
Hybrid linear + full attention
Layers · KV heads · head dim
24 · 2 · 256
KV cache
12 KB/token · 0.4 GB at 32K
Tool calling
good (from chat template)
Thinking
good (from chat template)
Vision
good (from config)
Commercial use
allowedRetain the required license and attribution notices
Import confidence
medium · capabilities estimated

Weights by quantization

Q3_K_M

0.5 GB

gguf file size

Q4_K_M

0.6 GB

gguf file size

Q5_K_M

0.7 GB

gguf file size

Q6_K

0.8 GB

gguf file size

Q8_0

1.0 GB

gguf file size

F16 / BF16

1.9 GB

gguf file size

  • • vision: good, inferred from config (low confidence).
  • • Capability ratings are estimated from model size and name — this model hasn't been assessed by hand.
  • • GGUF sizes come from community conversions matched by model name; equivalence and runtime support are not verified. MLX conversion availability is unverified.

MiniCPM-V-4.7-1B — 6-bit

Technically Runs for your workload

Technically Runs

Speed

110–150 tok/s

Excellent

Memory left

34 GB

of 48 GB

First word in

≈8 s

Excellent

All the details
Your setup
MacBook Pro M4 Pro 48 GB
Workload
Repository coding with Aider
Runtime → tool
LM Studio → Aider
Memory used
2.5 GB
Context
32K · up to 128K practical
Tool support
Official
Use-case fit
Poorly suited

Why?

  • Model fits with approximately 34 GB of memory headroom.
  • LM Studio supports hardware acceleration on this machine (Metal (Apple GPU)).
  • Aider can connect to LM Studio (officially supported).
  • Generation (110–150 tok/s) should be appropriate for interactive coding.
  • Ingesting a prompt of 14K tokens takes ≈8 s; prompt processing keeps up with interactive coding.
  • 32K working context is reasonable.
  • Weak coding capability for interactive coding.

Why “Technically Runs” rather than “Borderline”?

  • Workload suitability: Weak coding capability for interactive coding.

How sure are we?

Medium confidence

Estimated 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.
  • Hybrid/sliding attention performance varies more between runtimes.
Medium confidence
Check with your hardware and workload