on

Can the NVIDIA RTX Spark N1X (6144-core GPU) (128 GB) run Command R (08-2024) 32B?

58Good quality (B) · 58 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 66/100 (quality, fit, speed and memory use) sets the ranking.

Yes, it runs well

Runs well. At Q4_K_M it needs about 29.8 GB of 102 GB usable, with an estimated speed of 11.4 tok/s.

Best quant
Q4_K_M
Generation speed
11.4 tok/s
Prompt processing
642 tok/s
First token (1K prompt)
1.6 s
Largest safe context
128K

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

On Linux

Ollama

Command line + local API · runs on llama.cpp (ggml), MLX (Apple silicon, preview)

  • One command with Ollama’s own build of this model.
  • Serves an OpenAI-compatible API that other apps and coding tools can use.
ollama run command-r:35b-08-2024-q4_K_M
  • 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.
  • LM Studio Point-and-click: search, download and chat in one window.

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 Command R (08-2024) 32B

Recommended for the NVIDIA RTX Spark N1X (6144-core GPU) (128 GB): Q4_K_M. Every other quantization has its own download link in the table below.

Quickest · Ollama

One command downloads a ready-to-run version and starts a chat.

Get Ollama at ollama.com/download (opens in a new tab) · model page (opens in a new tab)

ollama run command-r:35b-08-2024-q4_K_M

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/lmstudio-community/c4ai-command-r-08-2024-GGUF (opens in a new tab)

ollama run hf.co/lmstudio-community/c4ai-command-r-08-2024-GGUF:Q4_K_M

Original weights · Hugging Face

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

huggingface.co/CohereLabs/c4ai-command-r-08-2024 (opens in a new tab)

Free Hugging Face account needed: accept the license on the model page and the download starts right away.

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

How it’s rated

Quality 58Good quality (B) · 58 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 66/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 well
How well it runs on the NVIDIA RTX Spark N1X (6144-core GPU) (128 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.26.5 / 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.8.0 / 15
Memory useRewards using the memory you have, so a bigger, better variant beats a tiny one that leaves most memory idle.6.7 / 15
Match score66.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) (128 GB)

Quant Memory needed Available Speed Runs Quality Download
Q2_K 23.1 GB 102 GB 18.7 tok/s Runs well 43Fair quality (C) · 43 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 59/100 (quality, fit, speed and memory use) sets the ranking.
Q3_K_M 26.0 GB 102 GB 14.7 tok/s Runs well 52Fair quality (C) · 52 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 63/100 (quality, fit, speed and memory use) sets the ranking. GGUF (Q3_K_L) (opens in a new tab)
Q4_K_M 29.8 GB 102 GB 11.4 tok/s Runs well 58Good quality (B) · 58 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 66/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q5_K_M 33.1 GB 102 GB 9.4 tok/s Slow 60Good quality (B) · 60 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 66/100 (quality, fit, speed and memory use) sets the ranking.
Q6_K 36.6 GB 102 GB 7.9 tok/s Slow 61Good quality (B) · 61 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 67/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q8_0 44.4 GB 102 GB 5.8 tok/s Slow 62Good quality (B) · 62 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 68/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
F16 74.7 GB 102 GB 2.7 tok/s Very slow 62Good quality (B) · 62 of 100: how capable the model is at F16, whatever it runs on. Match score 71/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

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?