Does Qwopus3.5-122B-A10B-Kimi-K2.6-destill-healed-abliterated fit in 16GB of VRAM?

Not at these settings. No indexed quantization of Qwopus3.5-122B-A10B-Kimi-K2.6-destill-healed-abliterated fits 16GB card at any context we compute, with f16 KV. The smallest shipped quantization is 42.66 GiB in weights alone, against 14.88 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 dtypef16q8_0q4_016 GB card, 14.88 GiB usable after overhead

Every quantization at every context

total memory required; green fits, red does not
QuantWeights4K8K16K32K64K128K
Q5_K_M82.62 GiB83.583.683.884.284.986.4
Q5_K_S80.03 GiB81.081.081.281.682.483.9
IQ4_NL76.06 GiB77.077.177.377.678.479.9
Q4_K_M70.63 GiB71.671.671.872.273.074.5
Q4_K_S66.19 GiB67.167.267.467.868.570.0
IQ4_XS62.92 GiB63.863.964.164.565.266.7
IQ3_M62.59 GiB63.563.663.864.264.966.4
Q3_K_L60.22 GiB61.161.261.461.862.564.0
Q3_K_M55.70 GiB56.656.756.957.358.059.5
IQ2_M55.04 GiB56.056.156.256.657.458.9
Q3_K_S50.30 GiB51.251.351.551.952.654.1
Q2_K42.66 GiB43.643.743.944.245.046.5
From the filePredictedwhat 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 there are no speeds on this page

A capacity is not a card. Whether a model fits depends only on memory, so every figure above holds for any 16GB accelerator. How fast it runs depends on memory bandwidth, which varies several-fold between cards of the same capacity — so putting a tokens-per-second number here would be inventing one. Pick a specific card from hardware and the speed column appears.

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, the KV cache grows linearly with context and, past about 32K, becomes larger than the weights for many models.