Boogu · text

Boogu-Image-0.1-Edit-Turbo

Boogu/Boogu-Image-0.1-Edit-Turbo

Boogu-Image-0.1-Edit-Turbo at Q4_0 is exactly 6,784,719,872 bytes (6.32 GiB / 6.78 GB) — an effective 5.274 bits per weight, not the nominal 4.

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

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
Q4_06.32 GiB6,784,719,8725.274chfm
Q4_06.32 GiB6,784,719,8725.274realrebelai
Q4_16.88 GiB7,384,902,6565.740realrebelai
Q4_16.88 GiB7,384,902,6565.740chfm
Q5_07.44 GiB7,985,089,1526.207chfm
Q5_07.44 GiB7,985,089,1526.207realrebelai
Q5_18.00 GiB8,585,271,9366.673chfm
Q5_18.00 GiB8,585,271,9366.673realrebelai
Q8_010.79 GiB11,586,196,9929.005chfm
Q8_010.79 GiB11,586,196,9929.005realrebelai

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_0 at roughly 5.39 GiB. The real file is 6.32 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-Edit-Turbo need?
Q4_0 is exactly 6,784,719,872 bytes (6.32 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-Edit-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.