KAT-Coder V2.5 Dev (35B-A3B) on NVIDIA L20

Can the NVIDIA L20 run KAT-Coder V2.5 Dev (35B-A3B)?

Yes, it runs great

Runs great. At Q8_0 it needs about 39.9 GB of 48.0 GB usable, with an estimated speed of 107 tok/s.

Best quant: Q8_0
Generation speed: 107 tok/s
Prompt processing: 14,352 tok/s
First token (1K prompt): 0.3 s
Largest safe context: 256K

Best app to run it on the NVIDIA L20

On Linux

vLLM

Inference server · runs on vLLM

The full model fits in GPU memory at 8-bit, so it can batch many requests: best for serving a team or an app.

vllm serve Kwaipilot/KAT-Coder-V2.5-Dev

LM Studio Point-and-click: search, download and chat in one window.
SGLang The full model fits in GPU memory at 8-bit, so it can batch many requests: best for serving a team or an app.

On Windows

LM Studio

Desktop app · runs on llama.cpp, MLX

Point-and-click: search, download and chat in one window.

Open KAT-Coder V2.5 Dev (35B-A3B) in LM Studio

llama.cpp Usually the first to support new model architectures.
Ollama Runs the Hugging Face GGUF with ollama run hf.co/…

Want an agent? KAT-Coder V2.5 Dev (35B-A3B) supports tool use, so you can pair a llama.cpp or MLX LM server with one of these. Apps that run on this computer come first.

Coding agents

Personal assistants

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 KAT-Coder V2.5 Dev (35B-A3B)

Recommended for the NVIDIA L20: Q8_0. Every other quantization has its own download link in the table below.

Quantized files · GGUF

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

Download the Q8_0 file (opens in a new tab)

huggingface.co/bartowski/Kwaipilot_KAT-Coder-V2.5-Dev-GGUF (opens in a new tab)

ollama run hf.co/bartowski/Kwaipilot_KAT-Coder-V2.5-Dev-GGUF:Q8_0

Original weights · Hugging Face

Full-precision files from Kuaishou, for fine-tuning, vLLM, Transformers.

huggingface.co/Kwaipilot/KAT-Coder-V2.5-Dev (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 91Excellent quality (A+) · 91 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 95/100 (quality, fit, speed and memory use) sets the ranking.: How capable the model itself is at Q8_0, 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 great: How well it runs on the NVIDIA L20: 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.	41.0 / 45
Memory fitFull marks when everything sits in GPU memory; fewer when part spills to system RAM.	25.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	96.0 / 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 L20

Quant	Memory needed	Available	Speed	Runs	Quality	Download
`Q2_K`	17.0 GB	48.0 GB	206 tok/s	Runs great	63Good quality (B) · 63 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 76/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q3_K_M`	20.2 GB	48.0 GB	184 tok/s	Runs great	76Great quality (A) · 76 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 84/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q4_K_M`	24.3 GB	48.0 GB	161 tok/s	Runs great	86Excellent quality (A+) · 86 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 90/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q5_K_M`	27.8 GB	48.0 GB	144 tok/s	Runs great	88Excellent quality (A+) · 88 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 93/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q6_K`	31.6 GB	48.0 GB	130 tok/s	Runs great	90Excellent quality (A+) · 90 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 95/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q8_0`	39.9 GB	48.0 GB	107 tok/s	Runs great	91Excellent quality (A+) · 91 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 95/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`F16`	72.5 GB	48.0 GB	—	Won't run	91Excellent quality (A+) · 91 of 100: how capable the model is at F16, whatever it runs on. Match score 12/100 (quality, fit, speed and memory use) sets the ranking.	GGUF · folder (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

91Excellent quality (A+) · 91 of 100: how capable the model is at F16, whatever it runs on. Match score 95/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA RTX PRO 6000 Blackwell F16 · 98.2 tok/s · Runs great
90Excellent quality (A+) · 90 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 95/100 (quality, fit, speed and memory use) sets the ranking. Apple M1 Max (64 GB) Q6_K · 72.3 tok/s · Runs great
90Excellent quality (A+) · 90 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 95/100 (quality, fit, speed and memory use) sets the ranking. Apple M4 Max (64 GB) Q6_K · 90.1 tok/s · Runs great
88Excellent quality (A+) · 88 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 94/100 (quality, fit, speed and memory use) sets the ranking. Apple M4 Pro (48 GB) Q5_K_M · 62.2 tok/s · Runs great
88Excellent quality (A+) · 88 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 94/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 5090 Q5_K_M · 194 tok/s · Runs great
91Excellent quality (A+) · 91 of 100: how capable the model is at F16, whatever it runs on. Match score 94/100 (quality, fit, speed and memory use) sets the ranking. Apple M2 Ultra (192 GB) F16 · 51.3 tok/s · Runs great

Quick answers

How much memory does KAT-Coder V2.5 Dev (35B-A3B) need on the NVIDIA L20 48GB?

At Q8_0 it needs about 39.9 GB. The NVIDIA L20 48GB has 48.0 GB usable.

How fast is KAT-Coder V2.5 Dev (35B-A3B) on the NVIDIA L20 48GB?

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

Which quantization of KAT-Coder V2.5 Dev (35B-A3B) should I use on the NVIDIA L20 48GB?

Q8_0. 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.