google · text

umt5-xxl

google/umt5-xxl

umt5-xxl at Q4_K_M is exactly 3,655,145,312 bytes (3.40 GiB / 3.66 GB) — an effective 5.147 bits per weight, not the nominal 4.

From the file· summed from 1 file(s)From the file· KV per layer
Parameters
5.7B
Architecture
t5encoder
null layers
Context
native (config.json)
License
apache-2.0

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
Q2_K2.36 GiB2,531,333,4083.565chatpig
Q3_K_S2.66 GiB2,858,489,6964.025city96
Q3_K_S2.66 GiB2,858,489,6964.025chatpig
Q3_K_M2.85 GiB3,055,097,6964.302chatpig
Q3_K_M2.85 GiB3,055,097,6964.302242city96
Q3_K_L3.00 GiB3,221,820,7044.537chatpig
IQ4_XS3.12 GiB3,348,436,8324.715242chatpig
Q4_03.23 GiB3,473,478,9444.891242chatpig
IQ4_NL3.25 GiB3,489,208,1604.914chatpig
Q4_K_S3.26 GiB3,497,596,7684.925chatpig
Q4_K_S3.26 GiB3,497,596,7684.925city96
Q4_K_M3.40 GiB3,655,145,3125.147chatpig
Q4_K_M3.40 GiB3,655,145,3125.147242city96
Q4_13.50 GiB3,762,885,9205.299chatpig
Q5_03.77 GiB4,052,292,8965.707chatpig
Q5_K_S3.77 GiB4,052,293,4725.707chatpig
Q5_K_S3.77 GiB4,052,293,4725.707city96
Q5_K_M3.86 GiB4,145,878,8805.838242chatpig
Q5_K_M3.86 GiB4,145,878,8805.838242city96
Q5_14.04 GiB4,341,699,8726.114chatpig
Q6_K4.35 GiB4,667,283,2966.573242chatpig
Q6_K4.35 GiB4,667,283,2966.573242city96
Q8_05.63 GiB6,043,068,2568.510242chatpig
Q8_05.63 GiB6,043,068,2568.510242city96
BF1610.59 GiB11,368,686,88016.010chatpig
F1610.59 GiB11,368,687,45616.010242city96
F1610.59 GiB11,368,687,45616.010242chatpig
F3221.17 GiB22,730,008,41632.009city96

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

Architecture

from config.json
Layers
Attention heads
KV heads
Head dim
Hidden size
Vocab
256,384
Sliding window
none
SWA period
MLA
no
Experts
Experts per token
use_sliding_window

Questions people ask

How much VRAM does umt5-xxl need?
Q4_K_M is exactly 3,655,145,312 bytes (3.40 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
Which quantization of umt5-xxl 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.