How much VRAM does GigaChat3-10B-A1.8B-base need?

Its published quantizations range from 6.03 GiB to 19.89 GiB in weights alone, before KV cache and runtime overhead.

GigaChat3-10B-A1.8B-base on Radeon RX 6500 XT

Can I run GigaChat3-10B-A1.8B-base on a Radeon RX 6500 XT?

Q: Can I run GigaChat3-10B-A1.8B-base on a Radeon RX 6500 XT?

No. No published quantization of GigaChat3-10B-A1.8B-base fits a Radeon RX 6500 XT at any context with q4_0 KV cache.

Not at these settings. No indexed quantization of GigaChat3-10B-A1.8B-base fits Radeon RX 6500 XT at any context we compute, with q4_0 KV. The smallest shipped quantization is 6.03 GiB in weights alone, against 3.72 GiB usable. CPU offload can still run it, slowly.

From the file· weights summed from filesFrom the file· KV computed per layerPredicted· speed and compute buffer

KV cache dtypef16 q8_0 q4_0— 4 GB card, 3.72 GiB usable after overhead

Every quantization at every context

total memory required; green fits, red does not

Quant	Weights●	4K◐	8K◐	16K◐	32K◐	64K◐	128K◐
BF16	19.89 GiB	20.8	20.9	20.9	21.0	21.3	21.8
Q8_0	10.57 GiB	11.5	11.5	11.6	11.7	12.0	12.5
Q6_K	8.18 GiB	9.1	9.1	9.2	9.3	9.6	10.1
Q4_K_M	6.03 GiB	7.0	7.0	7.1	7.2	7.4	8.0

●From the file◐Predictedwhat these mean

Figures are GiB of total memory: weights plus KV cache plus compute buffer and backend overhead. Weights and KV are near-exact; the overhead term is modeled. Hover any cell for the breakdown.

Why other calculators disagree

A parameters × bits ÷ 8 estimate ignores two things that dominate at long context. First, the weights themselves are not the nominal rate — quantizations are mixtures, so the real file is consistently larger than the label implies. Second, this model uses latent attention and allocates no V cache at all, so any formula reading num_key_value_heads overstates its cache by more than an order of magnitude.