MI

miniCPMmerge dpo bf16

MiniCPMGGUF by babybirdprdUpdated 2024-02-13
Download on Hugging Face
Parameters3.01B
Context2K
Layers40
Architecturellama
Smallest quant2.0 GB
Quick answer

miniCPMmerge dpo bf16 needs about 5.8 GB of memory at BF16 (a 2.2 GB file) with an 8K context window, so it fits on a 6 GB GPU. This repository has 3 quants, from 2.0 GB (BF16) to 3.2 GB (BF16).

miniCPMmerge dpo bf16 is a 3.01B-parameter MiniCPM model in GGUF format, quantized by babybirdprd. Its trained context length is 2K tokens. The repository has 3 quant files, from 2.0 GB (BF16) to 3.2 GB (BF16).

Quants & memory

QuantFileEst. memoryvs VRAMResultDownload
BF162.0 GB 3.2 GB
Fits Get file →
BF162.2 GB 3.5 GB
Fits Get file →
BF163.2 GB 4.5 GB
Fits Get file →

What GPU do you need for miniCPMmerge dpo bf16?

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: no quant fits at an 8K context.
  • 6 GB VRAM: the best quant that fits is BF16 (2.2 GB file, about 5.8 GB in use).
  • 8 GB VRAM: the best quant that fits is BF16 (3.2 GB file, about 6.7 GB in use).

Which miniCPMmerge dpo bf16 quant should you choose?

BF16 (2.2 GB) is the middle option in this repository. The unquantized model. It gives original quality and needs the most memory, so it is mainly for conversion or reference.

If memory is tight, the smallest file is BF16 at 2.0 GB, with the quality trade-offs that come with fewer bits. The unquantized model. It gives original quality and needs the most memory, so it is mainly for conversion or reference.

New to quant names? Read GGUF quantization explained.

Specifications

Architecture from the GGUF header

Architecturellama
Parameters3.01B
Layers40
Trained context2,048 tokens
KV cache (fp16)360 KB per token

Source

Quantized bybabybirdprd
FamilyMiniCPM
Downloads (HF)62
Last updated2024-02-13

Frequently asked questions about miniCPMmerge dpo bf16

How much VRAM does miniCPMmerge dpo bf16 need?

About 5.8 GB at BF16 with an 8K context window. That is the 2.2 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 miniCPMmerge dpo bf16 on an 8 GB GPU?

Yes, with BF16: the 3.2 GB file needs about 6.7 GB at 8K context. Larger quants in this repository do not fit in 8 GB.

What is the file size of miniCPMmerge dpo bf16 GGUF?

It depends on the quant: BF16 is 2.0 GB, BF16 is 2.2 GB, BF16 is 3.2 GB.

What context length does miniCPMmerge dpo bf16 support?

The GGUF header lists a trained context length of 2,048 tokens (2K). The KV cache grows with the context you use: about 3.0 GB at 8K and 0.8 GB at 2K.

Where can I download miniCPMmerge dpo bf16 GGUF?

The files are on Hugging Face in the babybirdprd/miniCPMmerge-dpo-bf16-GGUF repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.

Similar models

Browse all →

More from babybirdprd

All by babybirdprd →

More MiniCPM models

All MiniCPM →

Other tiny models

All tiny models →