dots.ocr

A parameters × bits ÷ 8 estimate puts I1-IQ1_S at roughly 1.59 GiB. The real file is 0.48 GiB, because a quantization is a mixture and some tensors are always kept at higher precision.

This model declares a sliding window but sets use_sliding_window: false, so the window is not applied. Honouring the field without the flag understates KV for the whole family.

How much VRAM does dots.ocr need?

I1-IQ1_S is exactly 513,101,760 bytes (0.48 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.

How large is dots.ocr's KV cache?

0.88 GiB at 32K context with an f16 cache, computed per layer. Quantizing the cache to q8_0 roughly halves it, which is often the difference between a context length fitting and not.

Which quantization of dots.ocr 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.