roboflow · text

rfdetr

roboflow/rfdetr

rfdetr at Q4_K is exactly 31,187,968 bytes (0.03 GiB / 0.03 GB) — an effective 8.449 bits per weight, not the nominal 4.

From the file· summed from 1 file(s)
Parameters
30M
Architecture
rfdetr
Context
native (config.json)
License
apache-2.0

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
Q4_K0.03 GiB31,187,9688.449mudler
Q4_K0.03 GiB32,752,5768.873mudler
Q4_K0.03 GiB33,385,1529.044mudler
Q8_00.04 GiB37,789,95210.237mudler
Q8_00.04 GiB40,083,64810.859mudler
Q8_00.04 GiB41,871,29611.343mudler
F160.06 GiB63,439,48817.186mudler
F160.06 GiB67,100,22418.178mudler
F160.07 GiB71,053,63219.249mudler
F320.11 GiB118,158,97632.010mudler
F320.12 GiB124,736,064mudler
F320.12 GiB133,309,760mudler

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 at roughly 0.02 GiB. The real file is 0.03 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 rfdetr need?
Q4_K is exactly 31,187,968 bytes (0.03 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
Which quantization of rfdetr 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.
rfdetr — VRAM requirements, exact quant sizes — ossmodeldb