DreamShaper 8 on AMD EPYC 7002 / 7003 series NAS (512 GB)

Can the AMD EPYC 7002 / 7003 series NAS (512 GB) run DreamShaper 8?

Yes, but slowly

Slow. At FP16 it needs about 2.8 GB of 471 GB usable, with an estimated speed of 49 s.

Best precision: FP16
Memory mode: Everything on GPU
Time per image: 49 s
Output: 512×512, 25 steps

Download DreamShaper 8

Original weights · Hugging Face

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

huggingface.co/Lykon/dreamshaper-8 (opens in a new tab)

No sign-in needed.

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

How it’s rated

Quality 40Fair quality (C) · 40 of 100: how capable the model is at FP16, whatever it runs on. Match score 49/100 (quality, fit, speed and memory use) sets the ranking.: How capable the model itself is at FP16, 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 Slow: How well it runs on the AMD EPYC 7002 / 7003 series NAS (512 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.	18.0 / 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.	25.0 / 25
SpeedGeneration speed against a 40 tokens/s target for LLMs, or render time against a target for image and video.	6.8 / 15
Memory useRewards using the memory you have, so a bigger, better variant beats a tiny one that leaves most memory idle.	0.1 / 15
Match score	49.9 / 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 AMD EPYC 7002 / 7003 series NAS (512 GB)

Quant	Memory needed	Available	Speed	Memory mode	Runs	Quality	Download
`FP16`	2.8 GB	471 GB	49 s	Everything on GPU	Slow	40Fair quality (C) · 40 of 100: how capable the model is at FP16, whatever it runs on. Match score 49/100 (quality, fit, speed and memory use) sets the ranking.	Original weights (opens in a new tab)

Other hardware that runs it

40Fair quality (C) · 40 of 100: how capable the model is at FP16, whatever it runs on. Match score 66/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 4060 FP16 · 4.3 s · Runs great
40Fair quality (C) · 40 of 100: how capable the model is at FP16, whatever it runs on. Match score 63/100 (quality, fit, speed and memory use) sets the ranking. Intel Arc B580 FP16 · 5.0 s · Runs great
40Fair quality (C) · 40 of 100: how capable the model is at FP16, whatever it runs on. Match score 63/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 3060 12GB FP16 · 4.9 s · Runs great
40Fair quality (C) · 40 of 100: how capable the model is at FP16, whatever it runs on. Match score 63/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 4070 SUPER FP16 · 2.3 s · Runs great
40Fair quality (C) · 40 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. AMD Radeon RX 9070 XT FP16 · 1.6 s · Runs great
40Fair quality (C) · 40 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. NVIDIA GeForce RTX 4060 Ti 16GB FP16 · 3.2 s · 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.