Can the Intel Arc A580 run MiniCPM-V 4.7 35B-A3B?

Yes, but slowly (heavy RAM offload)

Slow (heavy RAM offload). At Q4_K_M it needs about 22.6 GB of 8.0 GB usable, with an estimated speed of 32.9 tok/s.

Best quant: Q4_K_M
Generation speed: 32.9 tok/s
Prompt processing: 2,357 tok/s
First token (1K prompt): 0.4 s
Largest safe context: —

Best app to run it on the Intel Arc A580

On Windows

Command line + local API · runs on llama.cpp

Splits the model between GPU memory and system RAM, which this setup needs.
Gives you direct control of how many layers sit on the GPU, the best way to squeeze a model that doesn’t quite fit.
Supports Intel Arc through SYCL and Vulkan.

llama-server -hf openbmb/MiniCPM-V-4.7-35B-A3B-gguf:Q4_K_M

LM Studio Splits the model between GPU memory and system RAM, which this setup needs.
Jan Splits the model between GPU memory and system RAM, which this setup needs.

On Linux

llama.cpp

Command line + local API · runs on llama.cpp

Splits the model between GPU memory and system RAM, which this setup needs.
Gives you direct control of how many layers sit on the GPU, the best way to squeeze a model that doesn’t quite fit.
Supports Intel Arc through SYCL and Vulkan.

llama-server -hf openbmb/MiniCPM-V-4.7-35B-A3B-gguf:Q4_K_M

LM Studio Splits the model between GPU memory and system RAM, which this setup needs.
Jan Splits the model between GPU memory and system RAM, which this setup needs.

Want an agent? MiniCPM-V 4.7 35B-A3B supports tool use, so you can pair a llama.cpp or MLX LM server with one of these. Apps that run on this computer come first.

Coding agents

Personal assistants

How we choose: the files published for this model, your operating system and GPU, whether it fits fully in memory, and published speed tests (MLX vs llama.cpp on Apple silicon, vLLM vs llama.cpp vs Ollama on NVIDIA). Details.

Download MiniCPM-V 4.7 35B-A3B

Recommended for the Intel Arc A580: Q4_K_M. Every other quantization has its own download link in the table below.

Quantized files · GGUF

Works in LM Studio, llama.cpp, Jan and Ollama. No sign-in needed.

Download the Q4_K_M file (opens in a new tab)

huggingface.co/openbmb/MiniCPM-V-4.7-35B-A3B-gguf (opens in a new tab)

ollama run hf.co/openbmb/MiniCPM-V-4.7-35B-A3B-gguf:Q4_K_M

Original weights · Hugging Face

Full-precision files from OpenBMB, for fine-tuning, vLLM, Transformers.

huggingface.co/openbmb/MiniCPM-V-4.7-35B-A3B (opens in a new tab)

No sign-in needed.

Official repo · GitHub

Reference code, inference scripts and docs from OpenBMB. The weights themselves download from Hugging Face.

github.com/OpenBMB/MiniCPM-V (opens in a new tab)

git clone https://github.com/OpenBMB/MiniCPM-V

Links checked 1 day ago against Hugging Face, Ollama and GitHub.

How it’s rated

Quality 88Excellent quality (A+) · 88 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 72/100 (quality, fit, speed and memory use) sets the ranking.: How capable the model itself is at Q4_K_M, from its editorial quality tier scaled by the quantization or precision. It’s the same on any hardware that runs this variant. Scale: A+ 85+ · A 70+ · B 55+ · C 40+ · D under 40.
Runs Slowheavy RAM offload: How well it runs on the Intel Arc A580: speed, capped by how well it fits in memory. Runs great: 30+ tokens/s (or near the image, video or decision speed target) · Runs well: 10+ tokens/s · Slow: 3+ tokens/s · Very slow: under 3 · Won’t run: doesn’t fit even with offload. A tight fit or RAM offload caps it at Runs well; heavy offload caps it at Slow.

Match score

To order lists, each result also gets a match score out of 100 from four parts. It favors the most capable model that still runs well.

Model qualityEditorial quality tier of the model, scaled by the quantization or precision used.	39.9 / 45
Memory fitFull marks when everything sits in GPU memory; fewer when part spills to system RAM.	4.0 / 25
SpeedGeneration speed against a 40 tokens/s target for LLMs, or render time against a target for image and video.	13.6 / 15
Memory useRewards using the memory you have, so a bigger, better variant beats a tiny one that leaves most memory idle.	15.0 / 15
Match score	72.5 / 100

The match score orders results; it is not shown as a grade. Quality and Runs are the two ratings in the tables.

Every quantization on the Intel Arc A580

Quant	Memory needed	Available	Speed	Runs	Quality	Download
`Q2_K`	15.3 GB	8.0 GB	60.7 tok/s	Slowheavy RAM offload	65Good quality (B) · 65 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 63/100 (quality, fit, speed and memory use) sets the ranking.	GGUF files (opens in a new tab)
`Q3_K_M`	18.4 GB	8.0 GB	44.9 tok/s	Slowheavy RAM offload	78Great quality (A) · 78 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 69/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (IQ3_M) (opens in a new tab)
`Q4_K_M`	22.6 GB	8.0 GB	32.9 tok/s	Slowheavy RAM offload	88Excellent quality (A+) · 88 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 72/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q5_K_M`	26.2 GB	8.0 GB	26.4 tok/s	Slowheavy RAM offload	90Excellent quality (A+) · 90 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 71/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q6_K`	30.0 GB	8.0 GB	—	Won't run	92Excellent quality (A+) · 92 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 12/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q8_0`	38.5 GB	8.0 GB	—	Won't run	93Excellent quality (A+) · 93 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 12/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`F16`	71.6 GB	8.0 GB	—	Won't run	93Excellent quality (A+) · 93 of 100: how capable the model is at F16, whatever it runs on. Match score 12/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab) Original weights (opens in a new tab)

Memory figures assume 8K of context. Longer conversations or documents grow the KV cache.

Other hardware that runs it

93Excellent quality (A+) · 93 of 100: how capable the model is at F16, whatever it runs on. Match score 96/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA RTX PRO 6000 Blackwell F16 · 98.2 tok/s · Runs great
92Excellent quality (A+) · 92 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 96/100 (quality, fit, speed and memory use) sets the ranking. Apple M1 Max (64 GB) Q6_K · 72.3 tok/s · Runs great
92Excellent quality (A+) · 92 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 96/100 (quality, fit, speed and memory use) sets the ranking. Apple M4 Max (64 GB) Q6_K · 90.1 tok/s · Runs great
90Excellent quality (A+) · 90 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 95/100 (quality, fit, speed and memory use) sets the ranking. Apple M4 Pro (48 GB) Q5_K_M · 62.2 tok/s · Runs great
92Excellent quality (A+) · 92 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 95/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 5090 Q6_K · 179 tok/s · Runs well (tight fit)
93Excellent quality (A+) · 93 of 100: how capable the model is at F16, whatever it runs on. Match score 95/100 (quality, fit, speed and memory use) sets the ranking. Apple M2 Ultra (192 GB) F16 · 51.3 tok/s · Runs great

Estimates come from published hardware specs and our open formulas, not from running the model on your machine. Real speed varies with runtime, drivers and settings. Numbers marked “Measured” come from a linked benchmark.