Can the RTX 6000D run Ling 3.0 Tiny?

Yes. Ling 3.0 Tiny fits the RTX 6000D's 84 GB at Q4_K_M (about 6.8 GB needed), running at an estimated 180 tok/s. There's room for up to FP16 if you want higher quality.

VRAM
84 GB
Needs at Q4
6.8 GB
Headroom
77.2 GB
Speed (Q4_K_M)
~180 tok/s

Every quantization

Ling 3.0 Tiny (7.9B) on 84 GB

QuantWeightsNeedsFitEst. speed
Q4_K_M5 GB6.8 GBFits easily~180 tok/s
Q5_K_M6 GB7.8 GBFits easily~150 tok/s
Q8_08 GB9.8 GBFits easily~113 tok/s
FP1616 GB17.8 GBFits easily~56 tok/s

Estimates. Needs = weights + 1.8 GB for KV cache and runtime at modest context. Speed is single-stream decode scaled from the RTX 6000D's 1570 GB/s bandwidth (Estimated from memory bandwidth (llama.cpp decode)). Long contexts need more memory and run slower.

Run it

Copy, paste, go

llama-server -hf inclusionAI/Ling-3.0-tiny-GGUF -ngl 99

Ollama pulls a Q4 build by default. Pick a larger quant only if the table above says it fits. Full Ling 3.0 Tiny details →

Compare

Same model, other hardware - and other models on this card

Ling 3.0 Tiny on other hardware

Also runs on the RTX 6000D

Frequently asked

Quick answers

Can the RTX 6000D run Ling 3.0 Tiny?

Yes. Ling 3.0 Tiny fits the RTX 6000D's 84 GB at Q4_K_M (about 6.8 GB needed), running at an estimated 180 tok/s. There's room for up to FP16 if you want higher quality.

How much VRAM does Ling 3.0 Tiny need?

About 5 GB of weights at Q4_K_M, 8 GB at Q8_0 and 16 GB at FP16. Add roughly 1.8 GB for the KV cache and runtime at modest context lengths.

How fast is Ling 3.0 Tiny on the RTX 6000D?

Roughly 180 tokens per second at Q4_K_M (single user, llama.cpp-style decode). This is an estimate from the RTX 6000D's 1570 GB/s memory bandwidth.