DA

h2o danube3 500m chat

DanubeGGUF by DevQuasar-4Updated 2024-12-04
Download on Hugging Face
Parameters514M
Context8K
Layers16
Architecturellama
Smallest quant0.3 GB
Quick answer

h2o danube3 500m chat needs about 1.2 GB of memory at Q4_K_M (a 0.3 GB file) with an 8K context window, so it fits on a 4 GB GPU. This repository has 6 quants, from 0.3 GB (Q3_K_M) to 1.0 GB (F16).

h2o danube3 500m chat is a 514M-parameter Danube model in GGUF format, quantized by DevQuasar-4. Its trained context length is 8K tokens. The repository has 6 quant files, from 0.3 GB (Q3_K_M) to 1.0 GB (F16).

Quants & memory

QuantFileEst. memoryvs VRAMResultDownload
Q3_K_M0.3 GB 1.2 GB
Fits Get file →
Q4_K_M0.3 GB 1.2 GB
Fits Get file →
Q5_K_M0.4 GB 1.3 GB
Fits Get file →
Q6_K0.4 GB 1.3 GB
Fits Get file →
Q8_00.5 GB 1.4 GB
Fits Get file →
F161.0 GB 1.9 GB
Fits Get file →

What GPU do you need for h2o danube3 500m chat?

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 (1.0 GB file, about 1.9 GB in use).

Which h2o danube3 500m chat quant should you choose?

Q4_K_M is the usual starting point for h2o danube3 500m chat: it balances file size and quality well. Here it is a 0.3 GB file.

The Q8_0 file is 0.5 GB, about 1.7 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 Q3_K_M at 0.3 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

Architecturellama
Parameters514M
Layers16
Trained context8,192 tokens
KV cache (fp16)48 KB per token

Source

Quantized byDevQuasar-4
FamilyDanube
Licenseapache-2.0
Downloads (HF)341
Last updated2024-12-04

Frequently asked questions about h2o danube3 500m chat

How much VRAM does h2o danube3 500m chat need?

About 1.2 GB at Q4_K_M with an 8K context window. That is the 0.3 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 h2o danube3 500m chat on an 8 GB GPU?

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

What is the file size of h2o danube3 500m chat GGUF?

It depends on the quant: Q3_K_M is 0.3 GB, Q4_K_M is 0.3 GB, Q5_K_M is 0.4 GB, Q6_K is 0.4 GB, Q8_0 is 0.5 GB, F16 is 1.0 GB.

What context length does h2o danube3 500m chat support?

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

Where can I download h2o danube3 500m chat GGUF?

The files are on Hugging Face in the DevQuasar-4/h2o-danube3-500m-chat-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 h2o danube3 500m chat 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.

Other GGUFs of h2o-danube3-500m-chat

Similar models

Browse all →

More from DevQuasar-4

All by DevQuasar-4 →

More Danube models

All Danube →

Other tiny models

All tiny models →