The more images are in output folder the slower the startup is !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! HORRIBLE IDEA !!
Open
Potential Bug
- Dominant language
- Python
- Stars
- 133k
- Forks
- 15.7k
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 155
Description
### Expected Behavior
Why was it made like this ?! This is insanity, i checked it and renamed output folder - starts right away.
Its a matter of time when comfy becomes very unresponsive at startup and all workflows spit images to outputs folder.
This should be handled differently, please change this so it wont reload list of AAAALLLL IMAGES FROM OUTPUT FOLDER at startup.
I bet load image node is responsible for this crap.
seriously, its insane you left it like this.
### Actual Behavior
.
### Steps to Reproduce
jsut run comfy with lot of images in output folder, and then move the images somewhere else.
### Debug Logs
```powershell
.
```
### Other
.
Contributor guide
Assessment
This issue has not been assessed yet.