HY-OmniWeaving (8.3B, unified video) on Intel Core Ultra 200V (Arc 140V) (16 GB)

Can the Intel Core Ultra 200V (Arc 140V) (16 GB) run HY-OmniWeaving (8.3B, unified video)?

Barely: it runs very slowly (tight fit · CPU offload)

Very slow (tight fit · CPU offload). At FP8 it needs about 7.8 GB of 9.1 GB usable and takes about 1.8 h per clip.

Best precision: FP8
Memory mode: Sequential CPU offload
Time per clip: 1.8 h
Output: 848×480, 81 frames, 50 steps

Best app to run it on the Intel Core Ultra 200V (Arc 140V) (16 GB)

On Windows

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

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 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

Links checked 6 days ago against Hugging Face, Ollama and GitHub.

How it’s rated

Quality 74Great quality (A) · 74 of 100: how capable the model is at FP8, whatever it runs on. Match score 61/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 · CPU offload: How well it runs on the Intel Core Ultra 200V (Arc 140V) (16 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 unified memory the GPU can use; fewer when it goes past that limit.	10.0 / 25
SpeedGeneration speed against a 40 tokens/s target for LLMs, or render time against a target for image and video.	2.5 / 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 score	61.0 / 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 200V (Arc 140V) (16 GB)

Quant	Memory needed	Available	Speed	Memory mode	Runs	Quality	Download
`FP16`	10.7 GB	9.1 GB	—	—	Won't run	76Great quality (A) · 76 of 100: how capable the model is at FP16, whatever it runs on. Match score 10/100 (quality, fit, speed and memory use) sets the ranking.	Original weights (opens in a new tab)
`FP8`	7.8 GB	9.1 GB	1.8 h	Sequential CPU offload	Very slowtight fit · CPU offload	74Great quality (A) · 74 of 100: how capable the model is at FP8, whatever it runs on. Match score 61/100 (quality, fit, speed and memory use) sets the ranking.	Original weights (opens in a new tab)

Other hardware that runs it

74Great quality (A) · 74 of 100: how capable the model is at FP8, whatever it runs on. Match score 83/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 5090 FP8 · 6.7 min · Runs well
76Great quality (A) · 76 of 100: how capable the model is at FP16, whatever it runs on. Match score 79/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA RTX PRO 6000 Blackwell FP16 · 6.5 min · Runs well
74Great quality (A) · 74 of 100: how capable the model is at FP8, whatever it runs on. Match score 77/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 4090 FP8 · 8.3 min · Runs well (encoder in RAM)
74Great quality (A) · 74 of 100: how capable the model is at FP8, whatever it runs on. Match score 77/100 (quality, fit, speed and memory use) sets the ranking. AMD Radeon RX 7900 XTX FP8 · 9.3 min · Runs well (encoder in RAM)
74Great quality (A) · 74 of 100: how capable the model is at FP8, whatever it runs on. Match score 81/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA RTX 5000 Ada Generation FP8 · 9.5 min · Runs well
76Great quality (A) · 76 of 100: how capable the model is at FP16, whatever it runs on. Match score 81/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA H100 80GB SXM FP16 · 6.2 min · Runs well

Quick answers

How much memory does HY-OmniWeaving (8.3B, unified video) need on the Intel Core Ultra 200V (Arc 140V) 16GB?

At FP8 it needs about 7.8 GB. The Intel Core Ultra 200V (Arc 140V) 16GB has 9.1 GB usable.

How long does HY-OmniWeaving (8.3B, unified video) take on the Intel Core Ultra 200V (Arc 140V) 16GB?

About 1.8 h 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.