on

Can the Apple M1 Ultra (128 GB) run Ling 3.0 Flash (127B-A5B)?

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.

Yes, it runs well (tight fit)

Runs well (tight fit). At Q4_K_M it needs about 86.4 GB of 96.0 GB usable, with an estimated speed of 106 tok/s.

Best quant
Q4_K_M
Generation speed
106 tok/s
Prompt processing
2,553 tok/s
First token (1K prompt)
0.4 s
Largest safe context
200K

Best app to run it on the Apple M1 Ultra (128 GB)

On macOS

LM Studio

Desktop app · runs on llama.cpp, MLX

  • Point-and-click: search, download and chat in one window.

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

  • llama.cpp Usually the first to support new model architectures.
  • Ollama Runs the Hugging Face GGUF with ollama run hf.co/…

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)

Recommended for the Apple M1 Ultra (128 GB): 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 files (opens in a new tab)

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.

How it’s rated

Quality 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.
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 Runs welltight fit
How well it runs on the Apple M1 Ultra (128 GB): 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.35.1 / 45
Memory fitFull marks when the model fits in the share of unified memory the GPU can use; fewer when it goes past that limit.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 score89.1 / 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 Apple M1 Ultra (128 GB)

Quant Memory needed Available Speed Runs Quality Download
Q2_K 59.7 GB 96.0 GB 147 tok/s Runs great 57Good quality (B) · 57 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 80/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q3_K_M 71.1 GB 96.0 GB 126 tok/s Runs great 68Good quality (B) · 68 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 85/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q4_K_M 86.4 GB 96.0 GB 106 tok/s Runs welltight 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. GGUF · folder (opens in a new tab)
Q5_K_M 99.2 GB 96.0 GB 78.7 tok/s Runs wellover GPU memory limit 79Great quality (A) · 79 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 75/100 (quality, fit, speed and memory use) sets the ranking. GGUF · folder (opens in a new tab)
Q6_K 113 GB 96.0 GB 69.1 tok/s Slowfar over GPU memory limit 81Great quality (A) · 81 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 70/100 (quality, fit, speed and memory use) sets the ranking. GGUF · folder (opens in a new tab)
Q8_0 144 GB 96.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 264 GB 96.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

Quick answers

How much memory does Ling 3.0 Flash (127B-A5B) need on the M1 Ultra 128GB?

At Q4_K_M it needs about 86.4 GB. The M1 Ultra 128GB has 96.0 GB usable.

How fast is Ling 3.0 Flash (127B-A5B) on the M1 Ultra 128GB?

About 106 tok/s at Q4_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 M1 Ultra 128GB?

Q4_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.

Was this page helpful?