Boogu-Image-0.1-Turbo
Boogu/Boogu-Image-0.1-TurboBoogu-Image-0.1-Turbo at Q4_0 is exactly 13,624,953,664 bytes (12.69 GiB / 13.62 GB) — an effective 10.590 bits per weight, not the nominal 4.
Shipped quantizations
| Quant | Size● | Exact bytes● | Effective bpw● | Tensors● | Publisher |
|---|---|---|---|---|---|
| Q4_02 shards | 12.69 GiB | 13,624,953,664 | 10.590 | — | realrebelai |
| Q4_12 shards | 13.81 GiB | 14,825,319,232 | 11.523 | — | realrebelai |
| Q5_02 shards | 14.93 GiB | 16,025,692,224 | 12.456 | — | realrebelai |
| Q5_12 shards | 16.04 GiB | 17,226,057,792 | 13.389 | — | realrebelai |
| Q8_02 shards | 21.63 GiB | 23,227,907,904 | 18.054 | — | realrebelai |
Pipeline components
| Component | Size | Share | Can live on the CPU? |
|---|---|---|---|
| vae | 0.31 GiB | 2% | no, must be resident |
| denoiser | 19.17 GiB | 98% | no, must be resident |
| Full pipeline | 19.48 GiB | resident if nothing is offloaded | |
The parameter count published for a diffusion model describes the denoiser alone. Running it also requires its text encoder and VAE, and the text encoder is often nearly as large as the denoiser — which is why offloading it is the standard first move when you run out of memory.
We publish component sizes here, not throughput. Community-submitted image-generation rates do exist for many GPUs and we show them on the hardware pages, but they aggregate runs at different resolutions, step counts and settings, so they cannot be attributed to one model. Peak memory during sampling is unmeasured by any public source, and we do not estimate it.
Compare with
Will it run on your card?
Why other calculators give a different number
A parameters × bits ÷ 8 estimate puts Q4_0 at roughly 5.39 GiB. The real file is 12.69 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 Boogu-Image-0.1-Turbo need?
- Q4_0 is exactly 13,624,953,664 bytes (12.69 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
- Which quantization of Boogu-Image-0.1-Turbo 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.