on

Can the NVIDIA RTX Spark N1X (6144-core GPU) (32 GB) run Ling Mini 2.0 (16B-A1.4B)?

49Fair quality (C) · 49 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 77/100 (quality, fit, speed and memory use) sets the ranking.

Yes, it runs great

Runs great. At Q4_K_M it needs about 12.1 GB of 16.0 GB usable, with an estimated speed of 140 tok/s.

Best quant
Q4_K_M
Generation speed
140 tok/s
Prompt processing
14,811 tok/s
First token (1K prompt)
0.3 s
Largest safe context
32K

Best app to run it on the NVIDIA RTX Spark N1X (6144-core GPU) (32 GB)

On Linux

LM Studio

Desktop app · runs on llama.cpp, MLX

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

Open Ling Mini 2.0 (16B-A1.4B) in LM Studio

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

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 Mini 2.0 (16B-A1.4B)

Recommended for the NVIDIA RTX Spark N1X (6144-core GPU) (32 GB): Q4_K_M. 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 Q4_K_M file (opens in a new tab)

huggingface.co/inclusionAI/Ling-mini-2.0-GGUF (opens in a new tab)

ollama run hf.co/inclusionAI/Ling-mini-2.0-GGUF:Q4_K_M

Original weights · Hugging Face

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

huggingface.co/inclusionAI/Ling-mini-2.0 (opens in a new tab)

No sign-in needed.

Official repo · GitHub

Reference code, inference scripts and docs from Ant Group (inclusionAI). The weights themselves download from Hugging Face.

github.com/inclusionAI/Ling-V2 (opens in a new tab)

git clone https://github.com/inclusionAI/Ling-V2

Links checked 1 day ago against Hugging Face, Ollama and GitHub.

How it’s rated

Quality 49Fair quality (C) · 49 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 77/100 (quality, fit, speed and memory use) sets the ranking.
How capable the model itself is at Q4_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 great
How well it runs on the NVIDIA RTX Spark N1X (6144-core GPU) (32 GB): 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.2 / 45
Memory fitFull marks when the model fits in the share of unified memory the GPU can use; fewer when it goes past that limit.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 score77.2 / 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 Spark N1X (6144-core GPU) (32 GB)

Quant Memory needed Available Speed Runs Quality Download
Q2_K 8.7 GB 16.0 GB 184 tok/s Runs great 36Basic quality (D) · 36 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 68/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q3_K_M 10.2 GB 16.0 GB 162 tok/s Runs great 43Fair quality (C) · 43 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 74/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q4_K_M 12.1 GB 16.0 GB 140 tok/s Runs great 49Fair quality (C) · 49 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 77/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q5_K_M 13.8 GB 16.0 GB 123 tok/s Runs welltight fit 50Fair quality (C) · 50 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 76/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q6_K 15.5 GB 16.0 GB 110 tok/s Runs welltight fit 51Fair quality (C) · 51 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 77/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q8_0 19.5 GB 16.0 GB 75.4 tok/s Slowfar over GPU memory limit 52Fair quality (C) · 52 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 57/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
F16 34.7 GB 16.0 GB — Won't run 52Fair quality (C) · 52 of 100: how capable the model is at F16, whatever it runs on. Match score 7/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

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?