BugTraceAI · text

BugTraceAI-Apex-G4-26B-Master-f16

BugTraceAI/BugTraceAI-Apex-G4-26B-Master-f16

BugTraceAI-Apex-G4-26B-Master-f16 at Q4_K_M is exactly 16,796,011,040 bytes (15.64 GiB / 16.80 GB) — an effective 5.325 bits per weight, not the nominal 4.

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

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
TQ1_07.98 GiB8,570,953,7602.717piotreknow02
TQ2_08.71 GiB9,353,407,5202.965piotreknow02
Q2_K9.86 GiB10,582,732,3203.355piotreknow02
Q3_K_S11.38 GiB12,222,404,6403.875piotreknow02
Q3_K12.37 GiB13,286,728,7364.213piotreknow02
Q3_K_M12.37 GiB13,286,728,7364.213piotreknow02
Q3_K_L12.88 GiB13,824,483,3604.383piotreknow02
Q4_013.45 GiB14,439,356,9604.578piotreknow02
Q4_K_S14.40 GiB15,464,820,2564.903piotreknow02
Q4_114.87 GiB15,969,571,3605.063piotreknow02
Q4_K_M15.64 GiB16,796,011,0405.325piotreknow02
Q4_K15.64 GiB16,796,011,0405.325piotreknow02
Q5_016.30 GiB17,499,785,7605.548piotreknow02
Q5_K_S16.75 GiB17,986,728,4805.703piotreknow02
Q5_117.72 GiB19,030,000,1606.033piotreknow02
Q5_K_M17.82 GiB19,132,885,5366.066piotreknow02
Q5_K17.82 GiB19,132,885,5366.066piotreknow02
Q6_K21.08 GiB22,638,394,4007.177piotreknow02
Q8_025.02 GiB26,859,854,3688.516piotreknow02
F1647.04 GiB50,505,130,52816.012piotreknow02

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 13.22 GiB. The real file is 15.64 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 BugTraceAI-Apex-G4-26B-Master-f16 need?
Q4_K_M is exactly 16,796,011,040 bytes (15.64 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
Which quantization of BugTraceAI-Apex-G4-26B-Master-f16 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.