Qwen3Guard Gen 4B on NVIDIA RTX Spark N1X (6144-core GPU) (64 GB)

Can the NVIDIA RTX Spark N1X (6144-core GPU) (64 GB) run Qwen3Guard Gen 4B?

Yes, it runs well

Runs well. At Q6_K it needs about 8.4 GB of 48.0 GB usable and makes one decision in about 216 ms.

Best quant: Q6_K
Time per decision: 216 ms
Decisions per second: 4.6/s
Input assumed: 512 tokens
Returns: Fixed labels

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

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/Qwen3Guard-Gen-4B

LM Studio Point-and-click: search, download and chat in one window.
llama.cpp Usually the first to support new model architectures.

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 Qwen3Guard Gen 4B

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

huggingface.co/mradermacher/Qwen3Guard-Gen-4B-GGUF (opens in a new tab)

ollama run hf.co/mradermacher/Qwen3Guard-Gen-4B-GGUF:Q6_K

Original weights · Hugging Face

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

huggingface.co/Qwen/Qwen3Guard-Gen-4B (opens in a new tab)

No sign-in needed.

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

How it’s rated

Quality 83Great quality (A) · 83 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 84/100 (quality, fit, speed and memory use) sets the ranking.: How capable the model itself is at Q6_K, 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) (64 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.

PrecisionEditorial precision tier from the model’s published benchmarks, scaled by the quantization or precision used.	37.4 / 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
SpeedTime for one decision against a 100 ms target: reading the input plus any tokens the model writes.	10.2 / 15
ClarityHow easy the answer is to use in code: a probability or score earns the most, written feedback before a score the least.	12.0 / 15
Match score	84.6 / 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) (64 GB)

Quant	Memory needed	Available	Speed	Runs	Quality	Download
`Q4_K_M`	7.4 GB	48.0 GB	185 ms	Runs well	79Great quality (A) · 79 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 83/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q5_K_M`	7.9 GB	48.0 GB	200 ms	Runs well	81Great quality (A) · 81 of 100: how capable the model is at Q5_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)
`Q6_K`	8.4 GB	48.0 GB	216 ms	Runs well	83Great quality (A) · 83 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 84/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q8_0`	9.4 GB	48.0 GB	254 ms	Runs well	84Great quality (A) · 84 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 84/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`F16`	13.6 GB	48.0 GB	419 ms	Slow	84Great quality (A) · 84 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.	GGUF (opens in a new tab) Original weights (opens in a new tab)

Times are for one request with a 512-token input and about 6 tokens written. Batching servers process many requests at once.

Other hardware that runs it

84Great quality (A) · 84 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 89/100 (quality, fit, speed and memory use) sets the ranking. AMD Radeon RX 7900 XTX Q8_0 · 85 ms · Runs great
84Great quality (A) · 84 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 89/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 4090 Q8_0 · 84 ms · Runs great
84Great quality (A) · 84 of 100: how capable the model is at F16, whatever it runs on. Match score 89/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 5090 F16 · 85 ms · Runs great
84Great quality (A) · 84 of 100: how capable the model is at F16, whatever it runs on. Match score 89/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA RTX PRO 6000 Blackwell F16 · 80 ms · Runs great
84Great quality (A) · 84 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 89/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 5080 Q8_0 · 104 ms · Runs great
83Great quality (A) · 83 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 89/100 (quality, fit, speed and memory use) sets the ranking. AMD Radeon RX 9070 XT Q6_K · 98 ms · Runs great

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.