PH

Phoenix DPO 60B

PhoenixGGUF by cloudyuUpdated 2024-02-01
Download on Hugging Face
Parameters60.8B
Context4K
Layers60
Architecturellama
Smallest quant24.7 GB
Quick answer

Phoenix DPO 60B needs about 27.2 GB of memory at Q3_K_XS (a 24.7 GB file) with an 8K context window, so it fits on a 32 GB GPU. This repository has 2 quants, from 24.7 GB (Q3_K_XS) to 34.3 GB (Q4_0).

Phoenix DPO 60B is a 60.8B-parameter Phoenix model in GGUF format, quantized by cloudyu. Its trained context length is 4K tokens. The repository has 2 quant files, from 24.7 GB (Q3_K_XS) to 34.3 GB (Q4_0).

Quants & memory

QuantFileEst. memoryvs VRAMResultDownload
Q3_K_XS24.7 GB 26.2 GB
Too big Get file →
Q4_034.3 GB 35.8 GB
Too big Get file →

What GPU do you need for Phoenix DPO 60B?

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: no quant fits at an 8K context.
  • 8 GB VRAM: no quant fits at an 8K context.
  • 12 GB VRAM: no quant fits at an 8K context.
  • 16 GB VRAM: no quant fits at an 8K context.
  • 24 GB VRAM: no quant fits at an 8K context.
  • 32 GB VRAM: the best quant that fits is Q3_K_XS (24.7 GB file, about 27.2 GB in use).
  • 48 GB VRAM: the best quant that fits is Q4_0 (34.3 GB file, about 36.8 GB in use).

Which Phoenix DPO 60B quant should you choose?

Q3_K_XS (24.7 GB) is the middle option in this repository. 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
Parameters60.8B (approximate, mixture of experts)
Layers60
Trained context4,096 tokens
KV cache (fp16)240 KB per token

Source

Quantized bycloudyu
FamilyPhoenix
Downloads (HF)13
Last updated2024-02-01

Frequently asked questions about Phoenix DPO 60B

How much VRAM does Phoenix DPO 60B need?

About 27.2 GB at Q3_K_XS with an 8K context window. That is the 24.7 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 Phoenix DPO 60B on an 8 GB GPU?

Not at an 8K context. The smallest file needs about 27.2 GB, so you would need a larger GPU or CPU offloading.

What is the file size of Phoenix DPO 60B GGUF?

It depends on the quant: Q3_K_XS is 24.7 GB, Q4_0 is 34.3 GB.

What context length does Phoenix DPO 60B support?

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

Where can I download Phoenix DPO 60B GGUF?

The files are on Hugging Face in the cloudyu/Phoenix_DPO_60B_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 cloudyu

All by cloudyu →

More Phoenix models

All Phoenix →

Other large models

All large models →