granite-4.0-h-tiny-base

36 of 40 layers use linear attention, which keeps a fixed-size recurrent state instead of a per-token cache. Those layers do not grow with context at all — treating them as ordinary attention, as a flat formula does, overstates this model's cache by roughly 10.0× at long context.

A parameters × bits ÷ 8 estimate puts Q4_K_M at roughly 3.64 GiB. The real file is 3.94 GiB, because a quantization is a mixture and some tensors are always kept at higher precision.

How much VRAM does granite-4.0-h-tiny-base need?

Q4_K_M is exactly 4,230,969,888 bytes (3.94 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.

How large is granite-4.0-h-tiny-base's KV cache?

0.25 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 granite-4.0-h-tiny-base a mixture-of-experts model?

Yes — 64 experts, 6 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 granite-4.0-h-tiny-base 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.