on

Can the UP Squared Pro 7000 (16 GB) run PixArt-Σ XL 1024?

50Fair quality (C) · 50 of 100: how capable the model is at FP16, whatever it runs on. Match score 57/100 (quality, fit, speed and memory use) sets the ranking.

Yes, but slowly (encoder unloaded after use)

Slow (encoder unloaded after use). At FP16 it needs about 3.3 GB of 8.0 GB usable and takes about 65 s per image.

Best precision
FP16
Memory mode
Text encoder offloaded
Time per image
65 s
Output
1024×1024, 20 steps

Best app to run it on the UP Squared Pro 7000 (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 PixArt-Σ XL 1024

Original weights · Hugging Face

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

huggingface.co/PixArt-alpha/PixArt-Sigma-XL-2-1024-MS (opens in a new tab)

No sign-in needed.

Official repo · GitHub

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

github.com/PixArt-alpha/PixArt-sigma (opens in a new tab)

git clone https://github.com/PixArt-alpha/PixArt-sigma

How it’s rated

Quality 50Fair quality (C) · 50 of 100: how capable the model is at FP16, whatever it runs on. Match score 57/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 Slowencoder unloaded after use
How well it runs on the UP Squared Pro 7000 (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.22.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.20.0 / 25
SpeedGeneration speed against a 40 tokens/s target for LLMs, or render time against a target for image and video.5.9 / 15
Memory useRewards using the memory you have, so a bigger, better variant beats a tiny one that leaves most memory idle.9.5 / 15
Match score57.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 UP Squared Pro 7000 (16 GB)

Quant Memory needed Available Speed Memory mode Runs Quality Download
FP16 3.3 GB 8.0 GB 65 s Text encoder offloaded Slowencoder unloaded after use 50Fair quality (C) · 50 of 100: how capable the model is at FP16, whatever it runs on. Match score 57/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 PixArt-Σ XL 1024 need on the UP Squared Pro 7000 16GB?

At FP16 it needs about 3.3 GB. The UP Squared Pro 7000 16GB has 8.0 GB usable.

How long does PixArt-Σ XL 1024 take on the UP Squared Pro 7000 16GB?

About 65 s per image at FP16 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?