Open RuslanKuz opened 8 months ago
When I use SDXL loras and models I noticed that my SSD has many more writes than usual, and out of VRAM happens more frequently.
I have 12 GB VRAM and 32 GB DDR4 RAM, so to get to the point of using my SSD it is probably requring a lot of VRAM and memory.
same issue here, the last versions really slowed everything down for me, with a RTX3060 12Gb & 64Gb ddr. It's also become much more CPU intensive, and there is a weird pause at the beginning and end of every image generation, that is most often longer than the image generation itself (like 20 seconds to generate an image, with 15 seconds pause before it begins and after loading model and 10 seconds pause before writing the image to the disk after it finishes... why ?). Also the maximum size of images i can generate without OOM have gone down from 2200x2200px to 1700x1700px (more or less), and i need to restart webUI and browser every now and then because of memory leaks... Let's hope v2 will focus on optimization rather than adding more stuff
Do you have a paging file active? Try disabling that and see if there's less SSD churn, hopefully things should speed up too. Paging files are on by default in windows and essentially allow the OS to use some of the hard drive as RAM, which is generally a bad thing if you have enough hardware RAM available (32GB is a good start). The slowdown can be caused by context switching, dumping RAM to disk, and then reading it back into RAM, since RAM is much faster than the hard drive (no matter the hard drive).
Same issue on 1.9.4 Hard drive spikes to 50% usage, specifically when sdxl loras are loaded / unloaded. Once loaded (after 1 image generated and a few minutes), the performance stabilizes again, at least for me.
Checklist
What happened?
In general, I have a sad situation with the speed of SDXL generation with version 1.8 on a laptop with RTX 4050 6 GB. Generation 1024x1024 - 1:30-1:40 min with 30 steps. On version 1.7 it was 40-60 sec. This is with --xformers and --medvram-sdxl keys. At the same time on a home PC with RTX 3080 10 GB I didn't notice any special difference, maybe a little slower. It turns out that optimization for small video memory was not brought in for sure. Even more likely the opposite. I've installed clean setup v.1.7.0 and v.1.8.0 to test. Tested the same generation, ran several times. As a result, the best time:
Version 1.7.0 - 43.6 sec. Version 1.8.0 - 1.35 sec. Model - JuggernautXL 9. That's quite a downgrade. I noticed on monitoring that on 1.8 it loads video less. Probably because the memory is more clogged
Steps to reproduce the problem
What should have happened?
WebUI should generate faster like previous version 1.7.0
What browsers do you use to access the UI ?
Microsoft Edge
Sysinfo
sysinfo-2024-03-10-12-40.json
Console logs
Additional information
No any changes in PC hardware. Just upgraded a new version of WebUI. Previous version is working faster right now with this setup