EV

evomerge pareto

EvomergeGGUF by tellerlinUpdated 2026-06-11
Download on Hugging Face
Parameters1.54B
Context40K
Layers28
Architectureqwen3
Smallest quant0.9 GB
Quick answer

evomerge pareto needs about 3.3 GB of memory at Q8_0 (a 1.8 GB file) with an 8K context window, so it fits on a 4 GB GPU. This repository has 5 quants, from 0.9 GB (Q3_K_M) to 4.1 GB (Q3_K_M). Longer context needs more: at 32K tokens the KV cache alone adds about 3.8 GB.

evomerge pareto is a 1.54B-parameter Evomerge model in GGUF format, quantized by tellerlin. Its trained context length is 40K tokens. The repository has 5 quant files, from 0.9 GB (Q3_K_M) to 4.1 GB (Q3_K_M).

Quants & memory

QuantFileEst. memoryvs VRAMResultDownload
Q3_K_M0.9 GB 2.4 GB
Fits Get file →
Q8_01.6 GB 3.1 GB
Fits Get file →
Q8_01.8 GB 3.3 GB
Fits Get file →
Q3_K_M4.1 GB 5.6 GB
Fits Get file →
Q3_K_M4.1 GB 5.6 GB
Fits Get file →

What GPU do you need for evomerge pareto?

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 Q8_0 (1.8 GB file, about 3.3 GB in use).
  • 6 GB VRAM: the best quant that fits is Q3_K_M (4.1 GB file, about 5.6 GB in use).

Which evomerge pareto quant should you choose?

Q8_0 (1.8 GB) is the middle option in this repository. Close to lossless. It costs roughly twice the memory of a 4-bit file, so it suits cases where you have plenty of VRAM.

If memory is tight, the smallest file is Q3_K_M at 0.9 GB, with the quality trade-offs that come with fewer bits. A reasonable choice when a 4-bit file will not fit, mostly on larger models. Quality loss is noticeable but often acceptable.

New to quant names? Read GGUF quantization explained.

Specifications

Architecture from the GGUF header

Architectureqwen3
Parameters1.54B
Layers28
Trained context40,960 tokens
KV cache (fp16)112 KB per token

Source

Quantized bytellerlin
FamilyEvomerge
Licenseapache-2.0
Downloads (HF)48
Last updated2026-06-11

Frequently asked questions about evomerge pareto

How much VRAM does evomerge pareto need?

About 3.3 GB at Q8_0 with an 8K context window. That is the 1.8 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 evomerge pareto on an 8 GB GPU?

Yes, with Q3_K_M: the 4.1 GB file needs about 5.6 GB at 8K context. Larger quants in this repository do not fit in 8 GB.

What is the file size of evomerge pareto GGUF?

It depends on the quant: Q3_K_M is 0.9 GB, Q8_0 is 1.6 GB, Q8_0 is 1.8 GB, Q3_K_M is 4.1 GB, Q3_K_M is 4.1 GB.

What context length does evomerge pareto support?

The GGUF header lists a trained context length of 40,960 tokens (40K). The KV cache grows with the context you use: about 0.9 GB at 8K and 3.8 GB at 32K.

Where can I download evomerge pareto GGUF?

The files are on Hugging Face in the tellerlin/evomerge-pareto-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 evomerge pareto 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 Evomerge models

All Evomerge →

Other tiny models

All tiny models →