What GPU do I need to run arcee-ai/Trinity-Mini?

26.1B parameters, published in BF16. View on Hugging Face

26.1B
Parameters
BF16
Native precision
AfmoeForCausalLM
Architecture
text-generation
Pipeline

Trinity-Mini is published by arcee-ai on Hugging Face, with 20,724 downloads and 205 likes to date. It's a AfmoeForCausalLM model built for text-generation, published natively in BF16.

VRAM required & cheapest live GPU fit

Required VRAM = weight size at each precision times a flat 1.2 overhead for activations and fragmentation. The KV-cache grows with context and is not in that factor; it is listed per model below where the architecture is published. Full formula and assumptions: methodology.

PrecisionWeight sizeRequired VRAMCheapest live fitGPUs neededEst. $/hr (full fit)
BF1648.7 GB58.4 GBA1001$1.31/hr
cheaper alt.RTX A50003$0.528/hr
FP8 (quantized)24.3 GB29.2 GBRTX 5000 Ada1$0.539/hr
cheaper alt.RTX 5060 Ti2$0.361/hr
INT4 (quantized)12.2 GB14.6 GBRTX A40001$0.137/hr

A GPU is only matched to a row if its hardware supports that precision, and the primary recommendation is always a single-GPU fit when one exists.

INT4 requires a quantized checkpoint actually published for this model, check its Hugging Face page before relying on this row.

Cheapest way to run Trinity-Mini at its published (BF16) precision: 1× A100, at $1.31/hr per GPU ($1.31/hr total). Quantizing to FP8 or INT4 (rows above) can cost less, but requires a compatible quantized checkpoint to exist for this model.

Trinity-Mini: KV cache by context length

The KV cache is the memory the attention layers hold for every token of context, on top of the weights. It is not part of the flat 1.2x overhead in the table above, grows with context length and with every concurrent request, and is why a long-context deployment needs more VRAM than the table shows.

Sliding-window attention: windowed layers stop growing at the window, the full-attention layers keep growing. Cached per token: 65,536 bytes at 16-bit while the context is inside the window.

ContextKV cache, one sequence
4K0.16 GB
32K0.59 GB
128K2.1 GB

Computed from the layer, head and window counts in the model's own configuration (arcee-ai/Trinity-Mini), at 16 bits per cached value. Each concurrent sequence needs its own cache, on top of the weights.

Trinity-Mini: common questions

Can Trinity-Mini run on a single GPU?

Yes, but not on a desktop card. At BF16 it needs 58.4 GB of VRAM, more than a single 32 GB desktop card holds. The cheapest live single-card fit is a 80.0 GB A100 at $1.31/hr.

What is the least VRAM Trinity-Mini can run in?

14.6 GB, at INT4 (quantized), which fits a 16 GB card, against 58.4 GB at BF16. That row assumes an INT4 checkpoint has actually been published for this model, so check its Hugging Face page before planning around it.

Does quantizing Trinity-Mini lower the GPU bill?

Yes. At BF16 the cheapest live fit is one A100 at $1.31/hr. At INT4 (quantized) it drops to one RTX A4000 at $0.137/hr, provided a quantized checkpoint exists for it.

Weight-to-VRAM math, the fit rules, and how live prices are normalized: full methodology.

More Trinity models

All 3 Trinity models: VRAM and GPU requirements

Alternatives at this size

Other models for text-generation within about a third of Trinity-Mini's 26.1B parameters, from other model lines.

More on Trinity-Mini

Related reading: A100 pricing and specs, How much VRAM you need for LLMs, Serving LLMs with vLLM, vLLM vs TensorRT-LLM vs SGLang, and Best GPU for LLM inference.

Your own GPU cloud accounts

One console for the GPU clouds you already rent from. Your keys stay on your machine.

$20 a month, flat

Connect your accounts

One console for the GPU clouds you already use.

Connect your accounts for $20 a month, flat. Your provider bills the GPU.

© 2026 Aquanode. All rights reserved.

All trademarks, logos and brand names are the property of their respective owners.