on

Can the Apple M3 Ultra (512 GB) run Trinity Mini (26B-A3B)?

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

Yes, it runs great

Runs great. At F16 it needs about 83.7 GB of 384 GB usable, with an estimated speed of 52.2 tok/s.

Best quant
F16
Generation speed
52.2 tok/s
Prompt processing
5,869 tok/s
First token (1K prompt)
0.3 s
Largest safe context
128K

Best app to run it on the Apple M3 Ultra (512 GB)

On macOS

LM Studio

Desktop app · runs on llama.cpp, MLX · use the MLX build

  • Runs the MLX build, typically 35–90% faster than GGUF for a model with 3B active parameters on Apple silicon.
  • Point-and-click: search, download and chat in one window.

Open Trinity Mini (26B-A3B) in LM Studio

  • MLX LM Runs the MLX build, typically 35–90% faster than GGUF for a model with 3B active parameters on Apple silicon.
  • Unsloth Desktop Runs the MLX build, typically 35–90% faster than GGUF for a model with 3B active parameters on Apple silicon.

Want an agent? Trinity Mini (26B-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 Trinity Mini (26B-A3B)

Quantized files · GGUF

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

huggingface.co/arcee-ai/Trinity-Mini-GGUF (opens in a new tab)

ollama run hf.co/arcee-ai/Trinity-Mini-GGUF

Original weights · Hugging Face

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

huggingface.co/arcee-ai/Trinity-Mini (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 66Good quality (B) · 66 of 100: how capable the model is at F16, whatever it runs on. Match score 74/100 (quality, fit, speed and memory use) sets the ranking.
How capable the model itself is at F16, 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 great
How well it runs on the Apple M3 Ultra (512 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.29.7 / 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.25.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.5.0 / 15
Match score74.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 Apple M3 Ultra (512 GB)

Quant Memory needed Available Speed Runs Quality Download
Q2_K 41.9 GB 384 GB 191 tok/s Runs great 46Fair quality (C) · 46 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 (opens in a new tab)
Q3_K_M 44.3 GB 384 GB 169 tok/s Runs great 55Good quality (B) · 55 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 67/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q4_K_M 47.4 GB 384 GB 146 tok/s Runs great 62Good quality (B) · 62 of 100: how capable the model is at Q4_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)
Q5_K_M 50.0 GB 384 GB 130 tok/s Runs great 64Good quality (B) · 64 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 52.9 GB 384 GB 116 tok/s Runs great 65Good quality (B) · 65 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 72/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q8_0 59.2 GB 384 GB 94.2 tok/s Runs great 66Good quality (B) · 66 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 73/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
F16 83.7 GB 384 GB 52.2 tok/s Runs great 66Good quality (B) · 66 of 100: how capable the model is at F16, whatever it runs on. Match score 74/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?