on

Can the Intel Arc A770 16GB run Hunyuan A13B (80B-A13B)?

51Fair quality (C) · 51 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 51/100 (quality, fit, speed and memory use) sets the ranking.

Yes, but slowly (heavy RAM offload)

Slow (heavy RAM offload). At Q2_K it needs about 34.6 GB of 16.0 GB usable, with an estimated speed of 15.3 tok/s.

Best quant
Q2_K
Generation speed
15.3 tok/s
Prompt processing
988 tok/s
First token (1K prompt)
1.0 s
Largest safe context
—

Best app to run it on the Intel Arc A770 16GB

On Windows

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 tencent/Hunyuan-A13B-Instruct-GGUF:Q2_K
  • 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 tencent/Hunyuan-A13B-Instruct-GGUF:Q2_K
  • 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? Hunyuan A13B (80B-A13B) 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 Hunyuan A13B (80B-A13B)

Quantized files · GGUF

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

huggingface.co/tencent/Hunyuan-A13B-Instruct-GGUF (opens in a new tab)

ollama run hf.co/tencent/Hunyuan-A13B-Instruct-GGUF

Original weights · Hugging Face

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

huggingface.co/tencent/Hunyuan-A13B-Instruct (opens in a new tab)

No sign-in needed.

Official repo · GitHub

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

github.com/Tencent-Hunyuan/Hunyuan-A13B (opens in a new tab)

git clone https://github.com/Tencent-Hunyuan/Hunyuan-A13B

How it’s rated

Quality 51Fair quality (C) · 51 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 51/100 (quality, fit, speed and memory use) sets the ranking.
How capable the model itself is at Q2_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 Slowheavy RAM offload
How well it runs on the Intel Arc A770 16GB: 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.23.3 / 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.9.3 / 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 score51.6 / 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 A770 16GB

Quant Memory needed Available Speed Runs Quality Download
Q2_K 34.6 GB 16.0 GB 15.3 tok/s Slowheavy RAM offload 51Fair quality (C) · 51 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 51/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q3_K_M 41.9 GB 16.0 GB — Won't run 62Good quality (B) · 62 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 8/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q4_K_M 51.5 GB 16.0 GB — Won't run 70Great quality (A) · 70 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 9/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q5_K_M 59.6 GB 16.0 GB — Won't run 71Great quality (A) · 71 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 9/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q6_K 68.4 GB 16.0 GB — Won't run 73Great quality (A) · 73 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 9/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q8_0 87.7 GB 16.0 GB — Won't run 74Great quality (A) · 74 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 9/100 (quality, fit, speed and memory use) sets the ranking. GGUF · part 1 of 2 (opens in a new tab)
F16 163 GB 16.0 GB — Won't run 74Great quality (A) · 74 of 100: how capable the model is at F16, whatever it runs on. Match score 9/100 (quality, fit, speed and memory use) sets the ranking. 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?