connector · text

pig-1k

connector/pig-1k

pig-1k at Q4_K_M is exactly 40,239,547,872 bytes (37.48 GiB / 40.24 GB)

From the file· summed from 12 file(s)
Parameters
6.9B
Architecture
pig
Context
native (config.json)
License
mit

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
Q5_02 shards6.10 GiB6,547,694,3367.637calcuis
Q2_K4 shards7.85 GiB8,433,128,1929.837calcuis
Q4_13 shards11.42 GiB12,260,484,38414.301calcuis
Q4_05 shards13.15 GiB14,115,551,36016.465calcuis
Q5_13 shards13.65 GiB14,653,343,00817.092calcuis
F167 shards17.96 GiB19,288,953,24822.499calcuis
Q3_K_M12 shards29.04 GiB31,177,342,176calcuis
Q8_06 shards34.39 GiB36,924,555,936calcuis
Q4_K_M12 shards37.48 GiB40,239,547,872calcuis
Q5_K_M12 shards45.28 GiB48,623,274,464calcuis
Q6_K12 shards53.58 GiB57,531,100,896calcuis

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 3.59 GiB. The real file is 37.48 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 pig-1k need?
Q4_K_M is exactly 40,239,547,872 bytes (37.48 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
Which quantization of pig-1k 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.