Ling 3.0 Flash (127B-A5B) on NVIDIA RTX A6000

Can the NVIDIA RTX A6000 run Ling 3.0 Flash (127B-A5B)?

Yes, it runs well (offloads to RAM)

Runs well (offloads to RAM). At Q3_K_M it needs about 65.9 GB of 48.0 GB usable, with an estimated speed of 50.0 tok/s.

Best quant: Q3_K_M
Generation speed: 50.0 tok/s
Prompt processing: 4,370 tok/s
First token (1K prompt): 0.3 s
Largest safe context: —

Best app to run it on the NVIDIA RTX A6000

On Windows

LM Studio

Desktop app · runs on llama.cpp, MLX

Splits the model between GPU memory and system RAM, which this setup needs.
Point-and-click: search, download and chat in one window.

Open Ling 3.0 Flash (127B-A5B) in LM Studio

llama.cpp Splits the model between GPU memory and system RAM, which this setup needs.
Ollama Splits the model between GPU memory and system RAM, which this setup needs.

On Linux

LM Studio

Desktop app · runs on llama.cpp, MLX

Splits the model between GPU memory and system RAM, which this setup needs.
Point-and-click: search, download and chat in one window.

Open Ling 3.0 Flash (127B-A5B) in LM Studio

llama.cpp Splits the model between GPU memory and system RAM, which this setup needs.
Ollama Splits the model between GPU memory and system RAM, which this setup needs.

Want an agent? Ling 3.0 Flash (127B-A5B) 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 Ling 3.0 Flash (127B-A5B)

Quantized files · GGUF

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

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

ollama run hf.co/inclusionAI/Ling-3.0-flash-GGUF

Original weights · Hugging Face

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

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

No sign-in needed.

Links checked 2 days ago against Hugging Face, Ollama and GitHub.

How it’s rated

Quality 68Good quality (B) · 68 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 70/100 (quality, fit, speed and memory use) sets the ranking.: How capable the model itself is at Q3_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 Runs welloffloads to RAM: How well it runs on the NVIDIA RTX A6000: 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.	31.0 / 45
Memory fitFull marks when everything sits in GPU memory; fewer when part spills to system RAM.	10.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 score	71.0 / 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 NVIDIA RTX A6000

Quant	Memory needed	Available	Speed	Runs	Quality	Download
`Q2_K`	54.4 GB	48.0 GB	92.9 tok/s	Runs welloffloads to RAM	57Good quality (B) · 57 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 65/100 (quality, fit, speed and memory use) sets the ranking.	GGUF files (opens in a new tab)
`Q3_K_M`	65.9 GB	48.0 GB	50.0 tok/s	Runs welloffloads to RAM	68Good quality (B) · 68 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 70/100 (quality, fit, speed and memory use) sets the ranking.	GGUF files (opens in a new tab)
`Q4_K_M`	81.2 GB	48.0 GB	—	Won't run	77Great quality (A) · 77 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 10/100 (quality, fit, speed and memory use) sets the ranking.	GGUF · folder (opens in a new tab)
`Q5_K_M`	93.9 GB	48.0 GB	—	Won't run	79Great quality (A) · 79 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 10/100 (quality, fit, speed and memory use) sets the ranking.	GGUF · folder (opens in a new tab)
`Q6_K`	108 GB	48.0 GB	—	Won't run	81Great quality (A) · 81 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 10/100 (quality, fit, speed and memory use) sets the ranking.	GGUF · folder (opens in a new tab)
`Q8_0`	139 GB	48.0 GB	—	Won't run	82Great quality (A) · 82 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 11/100 (quality, fit, speed and memory use) sets the ranking.	GGUF · folder (opens in a new tab)
`F16`	258 GB	48.0 GB	—	Won't run	82Great quality (A) · 82 of 100: how capable the model is at F16, whatever it runs on. Match score 11/100 (quality, fit, speed and memory use) sets the ranking.	GGUF · folder (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

82Great quality (A) · 82 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 91/100 (quality, fit, speed and memory use) sets the ranking. Apple M3 Ultra (256 GB) Q8_0 · 65.0 tok/s · Runs great
81Great quality (A) · 81 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 91/100 (quality, fit, speed and memory use) sets the ranking. Apple M2 Ultra (192 GB) Q6_K · 81.3 tok/s · Runs great
81Great quality (A) · 81 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 90/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GB10 (128 GB) Q6_K · 39.2 tok/s · Runs well (tight fit)
77Great quality (A) · 77 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 90/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA RTX Spark N1X (6144-core GPU) (128 GB) Q4_K_M · 58.1 tok/s · Runs great
77Great quality (A) · 77 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 89/100 (quality, fit, speed and memory use) sets the ranking. AMD Ryzen AI Max+ 395 (128 GB) Q4_K_M · 45.0 tok/s · Runs well (tight fit)
77Great quality (A) · 77 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 89/100 (quality, fit, speed and memory use) sets the ranking. Apple M4 Max (128 GB) Q4_K_M · 82.0 tok/s · Runs well (tight fit)

Quick answers

How much memory does Ling 3.0 Flash (127B-A5B) need on the NVIDIA RTX A6000 48GB?

At Q3_K_M it needs about 65.9 GB. The NVIDIA RTX A6000 48GB has 48.0 GB usable.

How fast is Ling 3.0 Flash (127B-A5B) on the NVIDIA RTX A6000 48GB?

About 50.0 tok/s at Q3_K_M, an estimate from the hardware’s memory bandwidth and the size of the model.

Which quantization of Ling 3.0 Flash (127B-A5B) should I use on the NVIDIA RTX A6000 48GB?

Q3_K_M. Of the versions that fit, it is the one that runs best; when two run equally well, the check prefers the higher-rated one.

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.