on

Can the NVIDIA RTX Spark N1X (6144-core GPU) (48 GB) run HunyuanVideo 1.5 (8.3B)?

82Great quality (A) · 82 of 100: how capable the model is at FP8, whatever it runs on. Match score 73/100 (quality, fit, speed and memory use) sets the ranking.

Barely: it runs very slowly (tight fit · encoder unloaded after use)

Very slow (tight fit · encoder unloaded after use). At FP8 it needs about 29.9 GB of 32.2 GB usable, with an estimated speed of 62.5 min.

Best precision
FP8
Memory mode
Text encoder offloaded
Time per clip
62.5 min
Output
1280×720, 121 frames, 50 steps

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

On Linux

ComfyUI

Desktop app · runs on PyTorch (ComfyUI), GGUF via ComfyUI-GGUF

  • Runs this model with built-in or popular custom nodes; GGUF files load with ComfyUI-GGUF.

Get ComfyUI

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 HunyuanVideo 1.5 (8.3B)

Original weights · Hugging Face

Full-precision files from Tencent, for fine-tuning, vLLM, Transformers, Diffusers or ComfyUI.

huggingface.co/tencent/HunyuanVideo-1.5 (opens in a new tab)

No sign-in needed.

Official repo · GitHub

Reference code, inference scripts and docs from Tencent. The weights themselves download from Hugging Face.

github.com/Tencent-Hunyuan/HunyuanVideo-1.5 (opens in a new tab)

git clone https://github.com/Tencent-Hunyuan/HunyuanVideo-1.5

How it’s rated

Quality 82Great quality (A) · 82 of 100: how capable the model is at FP8, whatever it runs on. Match score 73/100 (quality, fit, speed and memory use) sets the ranking.
How capable the model itself is at FP8, 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 Very slowtight fit · encoder unloaded after use
How well it runs on the NVIDIA RTX Spark N1X (6144-core GPU) (48 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.37.0 / 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.18.0 / 25
SpeedGeneration speed against a 40 tokens/s target for LLMs, or render time against a target for image and video.3.3 / 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 score73.3 / 100

The match score orders results; it is not shown as a grade. Quality and Runs are the two ratings in the tables.

Every precision on the NVIDIA RTX Spark N1X (6144-core GPU) (48 GB)

Quant Memory needed Available Speed Memory mode Runs Quality Download
FP16 26.8 GB 32.2 GB 86.0 min Sequential CPU offload Very slowCPU offload 84Great quality (A) · 84 of 100: how capable the model is at FP16, whatever it runs on. Match score 67/100 (quality, fit, speed and memory use) sets the ranking. Original weights (opens in a new tab)
FP8 29.9 GB 32.2 GB 62.5 min Text encoder offloaded Very slowtight fit · encoder unloaded after use 82Great quality (A) · 82 of 100: how capable the model is at FP8, whatever it runs on. Match score 73/100 (quality, fit, speed and memory use) sets the ranking. Original weights (opens in a new tab)

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?