Can the NVIDIA T400 run Ling 3.0 Tiny (8B-A1.3B)?

Yes, it runs well (offloads to RAM)

Runs well (offloads to RAM). At Q3_K_M it needs about 4.9 GB of 4.0 GB usable, with an estimated speed of 71.7 tok/s.

Best quant: Q3_K_M
Generation speed: 71.7 tok/s
Prompt processing: 506 tok/s
First token (1K prompt): 2.0 s
Largest safe context: —

Best app to run it on the NVIDIA T400

On Windows

LM Studio

Desktop app · runs on llama.cpp, MLX

Splits the model between GPU memory and system RAM, which this setup needs.
Point-and-click: search, download and chat in one window.

Open Ling 3.0 Tiny (8B-A1.3B) in LM Studio

llama.cpp Splits the model between GPU memory and system RAM, which this setup needs.
Ollama Splits the model between GPU memory and system RAM, which this setup needs.

On Linux

LM Studio

Desktop app · runs on llama.cpp, MLX

Splits the model between GPU memory and system RAM, which this setup needs.
Point-and-click: search, download and chat in one window.

Open Ling 3.0 Tiny (8B-A1.3B) in LM Studio

llama.cpp Splits the model between GPU memory and system RAM, which this setup needs.
Ollama Splits the model between GPU memory and system RAM, which this setup needs.

How we choose: the files published for this model, your operating system and GPU, whether it fits fully in memory, and published speed tests (MLX vs llama.cpp on Apple silicon, vLLM vs llama.cpp vs Ollama on NVIDIA). Details.

Download Ling 3.0 Tiny (8B-A1.3B)

Quantized files · GGUF

Works in LM Studio, llama.cpp, Jan and Ollama. No sign-in needed.

huggingface.co/inclusionAI/Ling-3.0-tiny-GGUF (opens in a new tab)

ollama run hf.co/inclusionAI/Ling-3.0-tiny-GGUF

Original weights · Hugging Face

Full-precision files from Ant Group (inclusionAI), for fine-tuning, vLLM, Transformers.

huggingface.co/inclusionAI/Ling-3.0-tiny (opens in a new tab)

No sign-in needed.

Links checked 2 days ago against Hugging Face, Ollama and GitHub.

How it’s rated

Quality 50Fair quality (C) · 50 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 62/100 (quality, fit, speed and memory use) sets the ranking.: How capable the model itself is at Q3_K_M, from its editorial quality tier scaled by the quantization or precision. It’s the same on any hardware that runs this variant. Scale: A+ 85+ · A 70+ · B 55+ · C 40+ · D under 40.
Runs Runs welloffloads to RAM: How well it runs on the NVIDIA T400: speed, capped by how well it fits in memory. Runs great: 30+ tokens/s (or near the image, video or decision speed target) · Runs well: 10+ tokens/s · Slow: 3+ tokens/s · Very slow: under 3 · Won’t run: doesn’t fit even with offload. A tight fit or RAM offload caps it at Runs well; heavy offload caps it at Slow.

Match score

To order lists, each result also gets a match score out of 100 from four parts. It favors the most capable model that still runs well.

Model qualityEditorial quality tier of the model, scaled by the quantization or precision used.	22.7 / 45
Memory fitFull marks when everything sits in GPU memory; fewer when part spills to system RAM.	10.0 / 25
SpeedGeneration speed against a 40 tokens/s target for LLMs, or render time against a target for image and video.	15.0 / 15
Memory useRewards using the memory you have, so a bigger, better variant beats a tiny one that leaves most memory idle.	15.0 / 15
Match score	62.7 / 100

The match score orders results; it is not shown as a grade. Quality and Runs are the two ratings in the tables.

Every quantization on the NVIDIA T400

Quant	Memory needed	Available	Speed	Runs	Quality	Download
`Q2_K`	4.2 GB	4.0 GB	88.7 tok/s	Runs welloffloads to RAM	42Fair quality (C) · 42 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 58/100 (quality, fit, speed and memory use) sets the ranking.	GGUF files (opens in a new tab)
`Q3_K_M`	4.9 GB	4.0 GB	71.7 tok/s	Runs welloffloads to RAM	50Fair quality (C) · 50 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 62/100 (quality, fit, speed and memory use) sets the ranking.	GGUF files (opens in a new tab)
`Q4_K_M`	5.8 GB	4.0 GB	56.8 tok/s	Slowheavy RAM offload	57Good quality (B) · 57 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 59/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q5_K_M`	6.6 GB	4.0 GB	47.6 tok/s	Slowheavy RAM offload	58Good quality (B) · 58 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 60/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q6_K`	7.5 GB	4.0 GB	40.4 tok/s	Slowheavy RAM offload	59Good quality (B) · 59 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 60/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q8_0`	9.4 GB	4.0 GB	30.2 tok/s	Slowheavy RAM offload	60Good quality (B) · 60 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 59/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`F16`	16.8 GB	4.0 GB	—	Won't run	60Good quality (B) · 60 of 100: how capable the model is at F16, whatever it runs on. Match score 8/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab) Original weights (opens in a new tab)

Memory figures assume 8K of context. Longer conversations or documents grow the KV cache.

Other hardware that runs it

60Good quality (B) · 60 of 100: how capable the model is at F16, whatever it runs on. Match score 82/100 (quality, fit, speed and memory use) sets the ranking. AMD Radeon RX 7900 XTX F16 · 102 tok/s · Runs great
60Good quality (B) · 60 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 82/100 (quality, fit, speed and memory use) sets the ranking. Apple M4 (24 GB) Q8_0 · 41.8 tok/s · Runs great
60Good quality (B) · 60 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 82/100 (quality, fit, speed and memory use) sets the ranking. Apple M4 Pro (24 GB) Q8_0 · 79.0 tok/s · Runs great
60Good quality (B) · 60 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 82/100 (quality, fit, speed and memory use) sets the ranking. Intel Arc B580 Q8_0 · 102 tok/s · Runs great
60Good quality (B) · 60 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 82/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 3060 12GB Q8_0 · 104 tok/s · Runs great
60Good quality (B) · 60 of 100: how capable the model is at F16, whatever it runs on. Match score 82/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 3090 F16 · 109 tok/s · Runs great

Quick answers

How much memory does Ling 3.0 Tiny (8B-A1.3B) need on the NVIDIA T400 4GB?

At Q3_K_M it needs about 4.9 GB. The NVIDIA T400 4GB has 4.0 GB usable.

How fast is Ling 3.0 Tiny (8B-A1.3B) on the NVIDIA T400 4GB?

About 71.7 tok/s at Q3_K_M, an estimate from the hardware’s memory bandwidth and the size of the model.

Which quantization of Ling 3.0 Tiny (8B-A1.3B) should I use on the NVIDIA T400 4GB?

Q3_K_M. Of the versions that fit, it is the one that runs best; when two run equally well, the check prefers the higher-rated one.

Estimates come from published hardware specs and our open formulas, not from running the model on your machine. Real speed varies with runtime, drivers and settings. Numbers marked “Measured” come from a linked benchmark.