on

Can the Intel Core Ultra 5 225H NAS (32 GB) run HY-OmniWeaving (8.3B, unified video)?

74Great quality (A) · 74 of 100: how capable the model is at FP8, whatever it runs on. Match score 69/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 15.7 GB of 18.2 GB usable and takes about 86.5 min per clip.

Best precision
FP8
Memory mode
Text encoder offloaded
Time per clip
86.5 min
Output
848×480, 81 frames, 50 steps

Download HY-OmniWeaving (8.3B, unified video)

Original weights · Hugging Face

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

huggingface.co/tencent/HY-OmniWeaving (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/OmniWeaving (opens in a new tab)

git clone https://github.com/Tencent-Hunyuan/OmniWeaving

How it’s rated

Quality 74Great quality (A) · 74 of 100: how capable the model is at FP8, whatever it runs on. Match score 69/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 Intel Core Ultra 5 225H NAS (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.33.5 / 45
Memory fitFull marks when the model fits in the share of the NAS’s memory that models can use (the rest stays with the NAS system and its storage services); 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.2.8 / 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 score69.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 Intel Core Ultra 5 225H NAS (32 GB)

Quant Memory needed Available Speed Memory mode Runs Quality Download
FP16 10.7 GB 18.2 GB 2.0 h Sequential CPU offload Very slowCPU offload 76Great quality (A) · 76 of 100: how capable the model is at FP16, whatever it runs on. Match score 62/100 (quality, fit, speed and memory use) sets the ranking. Original weights (opens in a new tab)
FP8 15.7 GB 18.2 GB 86.5 min Text encoder offloaded Very slowtight fit · encoder unloaded after use 74Great quality (A) · 74 of 100: how capable the model is at FP8, whatever it runs on. Match score 69/100 (quality, fit, speed and memory use) sets the ranking. Original weights (opens in a new tab)

Other hardware that runs it

Quick answers

How much memory does HY-OmniWeaving (8.3B, unified video) need on the Intel Core Ultra 5 225H NAS 32GB?

At FP8 it needs about 15.7 GB. The Intel Core Ultra 5 225H NAS 32GB has 18.2 GB usable.

How long does HY-OmniWeaving (8.3B, unified video) take on the Intel Core Ultra 5 225H NAS 32GB?

About 86.5 min per clip at FP8 and default settings, an estimate scaled from a reference timing by this hardware’s compute speed.

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?