PA

PAVA M1

PavaGGUF by mradermacherUpdated 2025-07-29
Download on Hugging Face
Parameters109M
Context512
Layers12
Architecturebert
Smallest quant0.1 GB
Quick answer

PAVA M1 needs about 0.9 GB of memory at Q4_K_M (a 0.1 GB file) with an 8K context window, so it fits on a 4 GB GPU. This repository has 12 quants, from 0.1 GB (Q2_K) to 0.2 GB (F16).

PAVA M1 is a 109M-parameter Pava model in GGUF format, quantized by mradermacher. Its trained context length is 512 tokens. The repository has 12 quant files, from 0.1 GB (Q2_K) to 0.2 GB (F16).

Quants & memory

QuantFileEst. memoryvs VRAMResultDownload
Q2_K0.1 GB 0.6 GB
Fits Get file →
Q3_K_S0.1 GB 0.6 GB
Fits Get file →
Q3_K_M0.1 GB 0.6 GB
Fits Get file →
IQ4_XS0.1 GB 0.6 GB
Fits Get file →
Q3_K_L0.1 GB 0.6 GB
Fits Get file →
Q4_K_S0.1 GB 0.6 GB
Fits Get file →
Q4_K_M0.1 GB 0.6 GB
Fits Get file →
Q5_K_S0.1 GB 0.6 GB
Fits Get file →
Q5_K_M0.1 GB 0.6 GB
Fits Get file →
Q6_K0.1 GB 0.6 GB
Fits Get file →
Q8_00.1 GB 0.6 GB
Fits Get file →
F160.2 GB 0.7 GB
Fits Get file →

What GPU do you need for PAVA M1?

These figures add the file size, an fp16 KV cache at an 8K context window (worked out from this model’s own header) and about 0.5 GB for the runtime. They are estimates, so leave a little headroom, and expect to use less context or a smaller quant if you are right at the limit.

  • 4 GB VRAM: the best quant that fits is F16 (0.2 GB file, about 1.0 GB in use).

Which PAVA M1 quant should you choose?

Q4_K_M is the usual starting point for PAVA M1: it balances file size and quality well. Here it is a 0.1 GB file.

The Q8_0 file is 0.1 GB, about 1.6 times the size of Q4_K_M. It keeps the weights closer to the original, which only matters if you have the memory to spare.

If memory is tight, the smallest file is Q2_K at 0.1 GB, with the quality trade-offs that come with fewer bits. Use it only when memory is very tight. Expect a clear drop in quality, which is usually worse on small models and easier to live with on large ones.

New to quant names? Read GGUF quantization explained.

Specifications

Architecture from the GGUF header

Architecturebert
Parameters109M
Layers12
Trained context512 tokens
KV cache (fp16)36 KB per token

Source

Quantized bymradermacher
FamilyPava
Base modelcodegof/PAVA-M1
Licenseapache-2.0
Downloads (HF)36
Last updated2025-07-29

Frequently asked questions about PAVA M1

How much VRAM does PAVA M1 need?

About 0.9 GB at Q4_K_M with an 8K context window. That is the 0.1 GB file, plus the KV cache and roughly 0.5 GB of runtime overhead. Smaller quants need less and longer context needs more.

Can I run PAVA M1 on an 8 GB GPU?

Yes, with F16: the 0.2 GB file needs about 1.0 GB at 8K context. Larger quants in this repository do not fit in 8 GB.

What is the file size of PAVA M1 GGUF?

It depends on the quant: Q2_K is 0.1 GB, Q3_K_S is 0.1 GB, Q3_K_M is 0.1 GB, IQ4_XS is 0.1 GB, Q3_K_L is 0.1 GB, Q4_K_S is 0.1 GB and 6 more.

What context length does PAVA M1 support?

The GGUF header lists a trained context length of 512 tokens (512). The KV cache grows with the context you use: about 0.3 GB at 8K and 0.0 GB at 512.

Where can I download PAVA M1 GGUF?

The files are on Hugging Face in the mradermacher/PAVA-M1-GGUF repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.

What license does PAVA M1 use?

Hugging Face lists the license as apache-2.0. Licenses can differ between the quantized files and the original model, so check the repository and the base model before commercial use.

Similar models

Browse all →

More from mradermacher

All by mradermacher →

Other tiny models

All tiny models →