Trinity-Large-TrueBase

45 of 60 layers cache only a 4,096-token window rather than the full context, on a period of 4. Figures assume the default configuration; --swa-full disables the saving entirely.

A parameters × bits ÷ 8 estimate puts Q4_K_M at roughly 208.83 GiB. The real file is 225.04 GiB, because a quantization is a mixture and some tensors are always kept at higher precision. The larger discrepancy is the cache: a flat formula gives 7.50 GiB at 32K context where the real figure is 2.67 GiB, because most of this model's layers cache a fixed window rather than the whole context.

How much VRAM does Trinity-Large-TrueBase need?

Q4_K_M is exactly 241,632,208,032 bytes (225.04 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.

How large is Trinity-Large-TrueBase's KV cache?

2.67 GiB at 32K context with an f16 cache, computed per layer. Quantizing the cache to q8_0 roughly halves it, which is often the difference between a context length fitting and not.

Is Trinity-Large-TrueBase a mixture-of-experts model?

Yes — 256 experts, 4 routed per token. Every expert must be resident, but only the routed ones are read per token, which is why its memory requirement and its speed behave very differently.

Which quantization of Trinity-Large-TrueBase should I use?

Q4_K_M is the usual default. Pick the largest quantization that fits your card at the context you actually need — the table above gives exact sizes for every one published.