DavidAU · text

Llama-3.2-4X3B-MOE-Hell-California-10B

DavidAU/Llama-3.2-4X3B-MOE-Hell-California-10B

Llama-3.2-4X3B-MOE-Hell-California-10B at Q4_K_M is exactly 6,082,137,088 bytes (5.66 GiB / 6.08 GB) — an effective 4.891 bits per weight, not the nominal 4.

From the file· summed from 1 file(s)
Parameters
9.9B
Architecture
llama
Context
native (config.json)
License
apache-2.0

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
Q2_K3.53 GiB3,790,191,6163.048DavidAU
Q3_K_S4.13 GiB4,438,512,6403.569DavidAU
Q3_K_M4.54 GiB4,873,016,3203.918DavidAU
Q3_K_L4.90 GiB5,256,008,7044.226DavidAU
IQ4_XS5.08 GiB5,456,063,4884.387DavidAU
Q4_K_S5.35 GiB5,746,772,9924.621DavidAU
Q4_K_M5.66 GiB6,082,137,0884.891DavidAU
Q5_K_S6.43 GiB6,901,746,6885.550DavidAU
Q5_K_M6.61 GiB7,094,766,5925.705DavidAU
Q6_K7.61 GiB8,170,685,4406.570DavidAU
Q8_09.85 GiB10,580,055,0408.508DavidAU

Compare with

same modality, comparable size

Will it run on your card?

full quant x context sweep

Why other calculators give a different number

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

Architecture

Architecture unavailable — this repository is gated and no ungated mirror was found. Exact file sizes above are still authoritative; only the KV math needs the config.

Questions people ask

How much VRAM does Llama-3.2-4X3B-MOE-Hell-California-10B need?
Q4_K_M is exactly 6,082,137,088 bytes (5.66 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
Which quantization of Llama-3.2-4X3B-MOE-Hell-California-10B 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.