on

Can the Intel Arc A580 run Ling 3.0 Tiny (8B-A1.3B)?

59Good quality (B) · 59 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 80/100 (quality, fit, speed and memory use) sets the ranking.

Yes, it runs well (tight fit)

Runs well (tight fit). At Q6_K it needs about 7.7 GB of 8.0 GB usable, with an estimated speed of 133 tok/s.

Best quant
Q6_K
Generation speed
133 tok/s
Prompt processing
10,408 tok/s
First token (1K prompt)
0.3 s
Largest safe context
18K

Best app to run it on the Intel Arc A580

On Windows

llama.cpp

Command line + local API · runs on llama.cpp

  • Supports Intel Arc through SYCL and Vulkan.
  • Usually the first to support new model architectures.
llama-server -hf inclusionAI/Ling-3.0-tiny-GGUF:Q6_K
  • LM Studio Point-and-click: search, download and chat in one window.
  • Jan Point-and-click: search, download and chat in one window.

On Linux

llama.cpp

Command line + local API · runs on llama.cpp

  • Supports Intel Arc through SYCL and Vulkan.
  • Usually the first to support new model architectures.
llama-server -hf inclusionAI/Ling-3.0-tiny-GGUF:Q6_K
  • LM Studio Point-and-click: search, download and chat in one window.
  • Jan Point-and-click: search, download and chat in one window.

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 Ling 3.0 Tiny (8B-A1.3B)

Recommended for the Intel Arc A580: Q6_K. 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 Q6_K file (opens in a new tab)

huggingface.co/inclusionAI/Ling-3.0-tiny-GGUF (opens in a new tab)

ollama run hf.co/inclusionAI/Ling-3.0-tiny-GGUF:Q6_K

Original weights · Hugging Face

Full-precision files from Ant Group (inclusionAI), for fine-tuning, vLLM, Transformers.

huggingface.co/inclusionAI/Ling-3.0-tiny (opens in a new tab)

No sign-in needed.

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

How it’s rated

Quality 59Good quality (B) · 59 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 80/100 (quality, fit, speed and memory use) sets the ranking.
How capable the model itself is at Q6_K, 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 Runs welltight fit
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.26.7 / 45
Memory fitFull marks when everything sits in GPU memory; fewer when part spills to system RAM.24.0 / 25
SpeedGeneration speed against a 40 tokens/s target for LLMs, or render time against a target for image and video.15.0 / 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 score80.7 / 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 4.4 GB 8.0 GB 209 tok/s Runs great 42Fair quality (C) · 42 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 71/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q3_K_M 5.1 GB 8.0 GB 187 tok/s Runs great 50Fair quality (C) · 50 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 77/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q4_K_M 6.0 GB 8.0 GB 165 tok/s Runs great 57Good quality (B) · 57 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 80/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q5_K_M 6.8 GB 8.0 GB 148 tok/s Runs welltight fit 58Good quality (B) · 58 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 80/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q6_K 7.7 GB 8.0 GB 133 tok/s Runs welltight fit 59Good quality (B) · 59 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 80/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q8_0 9.6 GB 8.0 GB 71.2 tok/s Runs welloffloads to RAM 60Good quality (B) · 60 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 67/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
F16 17.0 GB 8.0 GB 20.8 tok/s Slowheavy RAM offload 60Good quality (B) · 60 of 100: how capable the model is at F16, whatever it runs on. Match score 56/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

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.

Was this page helpful?