Test · Render speed

Wan 2.2 Twice as Fast Without Losing Quality: SageAttention + Split CFG, Measured

Same PC, same Wan 2.2 image-to-video models, same images and seeds. Two changes, SageAttention and applying CFG only in the steps that need it, plus a newer ComfyUI, roughly halved render times. Here are the numbers straight from the logs, and frame comparisons so you can judge the quality yourself.

Published 27 October 2026 · By Vismantas Šleinota · Measured on RTX 5070 12GB, 64GB DDR5-6000, ComfyUI 0.40.0, PyTorch 2.14 (CUDA 13.0)

Quick answer: a Stable Scene clip (832×480, 81 frames) went from 15:31 to 8:49, Wild Mode (960×544, 53 frames) from about 23 to 10:47 minutes, and a 1536×864 / 57-frame clip that used to stall for hours now finishes in 29:55. Three things did it: SageAttention (each step ~1.6× faster), CFG 1 in the later high-noise steps (those steps become exactly 2× faster because the negative prompt is skipped), and ComfyUI 0.40 (no more VRAM stall). With the same seed the clips stay the same scene with the same characters and style. They are not pixel-identical, but none of the versions came out worse.
Honest scope: one PC, one RTX 5070, mainly one test image (six cartoon dogs) plus one earlier test with a photo of a woman. Times are from ComfyUI's own log ("Prompt executed in"). One number is calculated, not measured, and is marked as such. I build Loomance, and these settings are now its defaults (version 0.2), but everything here works in plain ComfyUI too.

The results

WorkflowBeforeAfterSpeed-up
Stable Scene, 832×480, 81 frames15:318:491.76×
Wild Mode, 960×544, 53 frames~23 min*10:47~2.1×
Stable Scene, 1536×864, 57 framesstalled (≈30 min per step)29:55finishes
First → Last Frame, 960×544, 57 framesnot measured8:06same recipe as Stable Scene

* Wild Mode without SageAttention and with the old CFG 0.9 was not rendered end to end. It is calculated from measured steps: the first stage took 11:25, and the second stage runs twice as slow at CFG 0.9 as at CFG 1.0 (measured with SageAttention: 40 vs 20 s/step). Measured neighbours: CFG 1.0 without SageAttention took 17:15, and CFG 0.9 with SageAttention took 14:01.

Where the time went (Stable Scene, 832×480, 81 frames, same seed)

SettingTime
Full CFG, no SageAttention (the old recipe)15:31
Split CFG, no SageAttention12:56
Full CFG, SageAttention~10:30
Split CFG + SageAttention (ComfyUI)8:39
Split CFG + SageAttention (inside Loomance 0.2)8:49

Change 1: CFG only where it matters

Wan 2.2 image-to-video uses two models: a high-noise model for the first half of the steps (it decides the motion and composition) and a low-noise model for the second half (it draws the details). With CFG above 1, ComfyUI runs the model twice per step: once with your prompt and once with the negative prompt. At exactly CFG 1 it skips the negative pass, so the step takes half the time. The log shows it plainly:

Same render, same high-noise modelCFG 1.7CFG 1.0
832×480, 81 frames (SageAttention)39 s/step19 s/step
1536×864, 57 frames (SageAttention)122 s/step61 s/step
960×544, 53 frames (no SageAttention)45 s/step22.5 s/step

The catch: CFG 1 everywhere doesn't work. In a test where the prompt asked a woman to take a sip of coffee, CFG 1 on every step made the action disappear. She just sat there. The first steps are where the prompt "wins" over the source image. So the high-noise stage is now split in two:

High-noise model, 24-step schedule:
  KSampler (Advanced)  steps 0–6   CFG 1.7   add_noise: enable   return_with_leftover_noise: enable
  KSampler (Advanced)  steps 6–12  CFG 1.0   add_noise: disable  return_with_leftover_noise: enable
Low-noise model:
  KSampler (Advanced)  steps 12–24 CFG 1.0   add_noise: disable  (unchanged)

For First → Last Frame the first part uses CFG 1.5, the rest is the same. Wild Mode is built differently (two passes with the low-noise model), and its second pass ran at CFG 0.9. Moving that to exactly 1.0 halved the second pass (40 → 20 s/step) and, as the frames below show, changed practically nothing.

Change 2: SageAttention

SageAttention computes the attention part of the model with 8-bit maths instead of 16-bit. In ComfyUI you enable it with the launch flag --use-sage-attention. Measured on the same Wild Mode render:

Wild Mode, 960×544, 53 frames, CFG 1.0Per stepTotal
PyTorch attention (default)34.3 s17:15
SageAttention21.2 s10:47

On Windows with ComfyUI portable you need three things in the embedded Python: triton-windows (we used "triton-windows<3.7"), Python's include and libs folders (the portable build doesn't ship them; the triton-windows README links ready-made ones), and a SageAttention wheel matching your PyTorch and CUDA major version (we used woct0rdho's Windows build, the cu130 torch2.10.0andhigher wheel). Test it before trusting it: run a few attention calls and compare them with PyTorch's own. The SageAttention author also warns that Wan can produce black or noisy output on some setups. We didn't see that on the RTX 5070, but it's why Loomance 0.2 runs that check on each user's GPU and falls back to normal attention if it fails.

Change 3: a newer ComfyUI

On the older ComfyUI build, 1536×864 with 57 frames ran out of VRAM on a 12GB card and slowed to about 1,800 seconds per step, so a single clip would take many hours (how that looks). In an earlier test, 53 frames at that size took about 56 minutes. ComfyUI 0.40 loads the model in pieces as needed ("dynamic VRAM loading" in the log). The same 57-frame render finished in 29:55 without any extra flags.

Does it still look the same?

To check, we rendered with a fixed seed, so the only difference between the clips is the setting. Then we compared every frame.

Wild Mode with the second pass at CFG 0.9 and at CFG 1.0, five frames each, same seed: the two columns look the same
Wild Mode, same seed. Left: second pass at CFG 0.9 (14:01). Right: CFG 1.0 (10:40). Average difference: 1.9 out of 255 per pixel, invisible to the eye.
Stable Scene with six cartoon dogs, same seed, three settings side by side at frames 1, 61, 121 and 161: same composition and characters, small differences in the puppies' poses later in the clip
Stable Scene, same seed. Left: SageAttention with full CFG. Middle: split CFG without SageAttention. Right: both (Loomance 0.2).
Zoomed puppies at frames 81 and 161 for the three settings: all clean, each with small differences where the puppies overlap
Zoomed in at frames 81 and 161. Each version has its own small flaw where the puppies overlap: an odd yellow shape on the right puppy's head (full CFG), two heads stacked (Loomance 0.2).

So the honest claim is "same quality, not identical frames": each setting gives an equally good, slightly different take of the same scene. If you compare tools or settings yourself, use a fixed seed. With random seeds the differences between two runs of the same settings are far bigger than anything shown here.

What we didn't use

Doing it in Loomance

Loomance 0.2 does all of this automatically: it updates its ComfyUI to 0.40 (about 2 GB; your models are kept), installs and tests SageAttention on your GPU, and uses the split-CFG workflows. If SageAttention fails the test or crashes, it renders without it. Videos are also 32 fps now: Wan generates 16 fps motion and Loomance doubles the frames with RIFE, so 32 fps is natural speed.

Tools and sources

Related articles

VŠ

Vismantas Šleinota builds Loomance, a free local AI animation app, as a solo project in Lithuania, and discusses local AI video as u/noise_to_motion on Reddit. Every clip and time on this page comes from his own PC. Got different numbers on your card? Send them to [email protected].


Frequently asked questions

Does SageAttention lower Wan 2.2 quality?
Not visibly in our tests. With the same seed, SageAttention changes the pixels about as much as the CFG change does (an average of about 5 out of 255 per pixel in the second half of the clip), so the clip is a slightly different take of the same scene, not a worse one. Characters, style and colours stayed the same. We saw no black or noisy frames on an RTX 5070.
Why not use CFG 1 for every step?
CFG 1 skips the negative prompt and halves the time per step, but in our test with CFG 1 everywhere the action disappeared: the woman never took the sip the prompt asked for. The first steps decide what happens in the clip, so we keep the original CFG there (1.7 for Stable Scene, 1.5 for First → Last) and use CFG 1 only for the later high-noise steps.
Why did 1536×864 renders stall before?
On the older ComfyUI build a 57-frame 1536×864 render on a 12GB card ran out of VRAM and fell back to a crawl: one step took about 30 minutes. ComfyUI 0.40 loads the model dynamically and the same render finished in 29:55.
Will this work on RTX 30 or 40 cards?
SageAttention 2 has kernels for RTX 30, 40 and 50 cards, but we only measured an RTX 5070. The speed-up from CFG 1 (skipping the negative prompt) works on any card. Loomance 0.2 installs SageAttention, tests it on your GPU first, and runs without it if the test fails.

Get the faster workflow without the setup

Loomance is free to use (ad-supported) and renders locally on your NVIDIA GPU. Version 0.2 sets up ComfyUI, Wan 2.2 and SageAttention for you. No node graphs, no cloud uploads.

Download free