on

Can the NVIDIA RTX 6000 Ada Generation run Qwen1.5 MoE A2.7B Chat?

24Basic quality (D) · 24 of 100: how capable the model is at F16, whatever it runs on. Match score 65/100 (quality, fit, speed and memory use) sets the ranking.

Yes, it runs great

Runs great. At F16 it needs about 33.3 GB of 48.0 GB usable, with an estimated speed of 70.7 tok/s.

Best quant
F16
Generation speed
70.7 tok/s
Prompt processing
24,293 tok/s
First token (1K prompt)
0.3 s
Largest safe context
8K

Best app to run it on the NVIDIA RTX 6000 Ada Generation

On Windows

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.
  • On Windows it runs through WSL2.
vllm serve Qwen/Qwen1.5-MoE-A2.7B-Chat
  • 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.
  • Docker Model Runner Handy if you already work in Docker.

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 Qwen/Qwen1.5-MoE-A2.7B-Chat
  • 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.
  • Docker Model Runner Handy if you already work in Docker.

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 Qwen1.5 MoE A2.7B Chat

Original weights · Hugging Face

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

huggingface.co/Qwen/Qwen1.5-MoE-A2.7B-Chat (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 24Basic quality (D) · 24 of 100: how capable the model is at F16, whatever it runs on. Match score 65/100 (quality, fit, speed and memory use) sets the ranking.
How capable the model itself is at F16, 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 RTX 6000 Ada Generation: 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.10.8 / 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 score65.8 / 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 RTX 6000 Ada Generation

Quant Memory needed Available Speed Runs Quality Download
Q2_K 10.3 GB 48.0 GB 221 tok/s Runs great 16Basic quality (D) · 16 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 52/100 (quality, fit, speed and memory use) sets the ranking. All files (opens in a new tab)
Q3_K_M 11.6 GB 48.0 GB 199 tok/s Runs great 20Basic quality (D) · 20 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 54/100 (quality, fit, speed and memory use) sets the ranking. All files (opens in a new tab)
Q4_K_M 13.3 GB 48.0 GB 177 tok/s Runs great 22Basic quality (D) · 22 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 56/100 (quality, fit, speed and memory use) sets the ranking. All files (opens in a new tab)
Q5_K_M 14.8 GB 48.0 GB 159 tok/s Runs great 23Basic quality (D) · 23 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 57/100 (quality, fit, speed and memory use) sets the ranking. All files (opens in a new tab)
Q6_K 16.4 GB 48.0 GB 145 tok/s Runs great 23Basic quality (D) · 23 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 58/100 (quality, fit, speed and memory use) sets the ranking. All files (opens in a new tab)
Q8_0 19.8 GB 48.0 GB 120 tok/s Runs great 24Basic quality (D) · 24 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 60/100 (quality, fit, speed and memory use) sets the ranking. All files (opens in a new tab)
F16 33.3 GB 48.0 GB 70.7 tok/s Runs great 24Basic quality (D) · 24 of 100: how capable the model is at F16, whatever it runs on. Match score 65/100 (quality, fit, speed and memory use) sets the ranking. 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

Quick answers

How much memory does Qwen1.5 MoE A2.7B Chat need on the NVIDIA RTX 6000 Ada Generation 48GB?

At F16 it needs about 33.3 GB. The NVIDIA RTX 6000 Ada Generation 48GB has 48.0 GB usable.

How fast is Qwen1.5 MoE A2.7B Chat on the NVIDIA RTX 6000 Ada Generation 48GB?

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

Which quantization of Qwen1.5 MoE A2.7B Chat should I use on the NVIDIA RTX 6000 Ada Generation 48GB?

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

Was this page helpful?