Comfy-Org / Comfy-Org/ComfyUI

Windows memory compression feature - maybe a thing to take advantage of more in ComfyUI? (if it is not already the case)

Open
#10,739 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
133k
Forks
15.7k
Avg merge
1d 7h
Merged PRs (30d)
158

Description

Hi, I noticed recently looking at the Task Manager that, during some stages in prompt execution, the compressed memory area gets to prety important size (this is for example during WAN 2.2 low noise ksampler or right after that, during VAE decoding):

Image

I mean, **16 GB** compressed when you have only 9 GB still available, that might mean a lot of disk swapping avoided. I observed those hefty compressed sizes relatively recently, I mean last 1.5-2 months maybe. I was used to see in general about 0 GB compressed. It might be the case I wasn't paying attention before. Or it might be the case that something in Windows 11 changed with the release of 25H2. Or it might be due to pinned memory feature? I am not sure.

Anyway, I opened this to suggest to ComfyUI team to consider taking advantage of this Windows feature while making future optimizations, in the case they have not already done so. I'm not sure there is anything to do here to optimize but I thought to say something anyway.

And in relation to that, maybe some tips for the users might be very helpful at some point, or some settings in windows less known or obvious that might be optimized for the use case of ComfyUI. Like what's best to set this option to, Programs or Background services?

Image

Thanks!

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.