tencent · text · mixture of experts

Hy3

tencent/Hy3

Hy3 at Q4_K_M is exactly 180,999,059,328 bytes (168.57 GiB / 181.00 GB) — an effective 4.846 bits per weight, not the nominal 4. Its KV cache at 32K is 10.00 GiB.

From the file· summed from 4 file(s)From the file· KV per layer
Parameters
299B
total, not active
Architecture
hy_v3
80 layers
Context
262,144
native (config.json)
License
apache-2.0

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
IQ1_S2 shards59.65 GiB64,051,148,3521.715bartowski
IQ1_M2 shards66.22 GiB71,100,724,8001.904bartowski
IQ2_XXS3 shards76.47 GiB82,113,918,6562.199bartowski
IQ1_M83.30 GiB89,446,312,3842.395AngelSlim
IQ2_XS3 shards84.81 GiB91,060,369,1202.438bartowski
IQ1_M2 shards85.45 GiB91,756,066,4642.457vcruz305
IQ2_S3 shards86.43 GiB92,805,134,0162.485bartowski
IQ2_M3 shards93.14 GiB100,008,834,8162.678vcruz305
IQ2_M3 shards95.08 GiB102,091,323,1042.733bartowski
Q2_K3 shards99.36 GiB106,691,229,3762.857bartowski
Q2_K_L3 shards99.81 GiB107,174,557,4082.870bartowski
Q2_K3 shards101.28 GiB108,748,601,1202.912vcruz305
IQ3_XXS3 shards109.28 GiB117,335,832,3523.142vcruz305
IQ3_XXS4 shards117.43 GiB126,089,361,2483.376bartowski
Q3_K_S4 shards122.26 GiB131,274,569,5363.515bartowski
Q3_K_M125.35 GiB134,597,913,0243.6041278AngelSlim
IQ3_XS4 shards128.00 GiB137,437,050,6563.680bartowski
Q3_K_M4 shards128.10 GiB137,545,479,9683.683bartowski
Q3_K_M3 shards132.94 GiB142,740,092,6723.822vcruz305
Q3_K_L4 shards133.25 GiB143,077,766,9763.831bartowski
IQ3_M4 shards133.80 GiB143,668,639,5843.847bartowski
IQ4_XS4 shards148.22 GiB159,152,175,0084.261vcruz305
IQ4_XS5 shards149.73 GiB160,771,307,4564.305bartowski
IQ4_NL5 shards158.14 GiB169,803,872,1924.546bartowski
Q4_05 shards158.62 GiB170,321,082,3364.560bartowski
Q4_K_S5 shards163.41 GiB175,458,318,3044.698bartowski
Q4_K_M4 shards168.57 GiB180,999,059,3284.846vcruz305
Q4_K_M5 shards169.65 GiB182,158,227,3604.877bartowski
Q4_K_M169.81 GiB182,328,371,6484.8821278AngelSlim
Q4_K_L5 shards169.99 GiB182,525,556,6404.887bartowski
Q4_15 shards174.90 GiB187,795,601,3445.028bartowski
Q5_K_S6 shards191.88 GiB206,034,401,3445.517bartowski
Q5_K_M5 shards197.61 GiB212,177,942,5285.681vcruz305
Q5_K_M6 shards198.22 GiB212,837,857,3445.699bartowski
Q6_K7 shards239.58 GiB257,246,623,9366.888bartowski
Q8_07 shards295.84 GiB317,652,367,2968.505vcruz305
Q8_09 shards295.84 GiB317,652,367,7768.505bartowski

KV cache by context

computed per layer
ContextKV cache (f16)Flat formulaOverstated byFull / windowed / recurrent
4,0961.25 GiB1.25 GiB80 / 0 / 0
8,1922.50 GiB2.50 GiB80 / 0 / 0
16,3845.00 GiB5.00 GiB80 / 0 / 0
32,76810.00 GiB10.00 GiB80 / 0 / 0
65,53620.00 GiB20.00 GiB80 / 0 / 0
131,07240.00 GiB40.00 GiB80 / 0 / 0

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 156.52 GiB. The real file is 168.57 GiB, because a quantization is a mixture and some tensors are always kept at higher precision.

Architecture

from config.json
Layers
80
Attention heads
64
KV heads
8
Head dim
128
Hidden size
4096
Vocab
120,832
Sliding window
none
SWA period
MLA
no
Experts
192
Experts per token
8
use_sliding_window

Questions people ask

How much VRAM does Hy3 need?
Q4_K_M is exactly 180,999,059,328 bytes (168.57 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
How large is Hy3's KV cache?
10.00 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 Hy3 a mixture-of-experts model?
Yes — 192 experts, 8 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 Hy3 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.