History: Slow UI from large number of generated images

[Evil-Dragon]

Describe the bug
If you have a large amount of generated images, i.e. over 20k, the history function will cause massive UI slowdowns and cause everything to be sluggish. I suspect this is because it's pulling in too many images/data?

To Reproduce
Steps to reproduce the behavior:

1. Create a lot of AI images
2. Load up UI
3. Everything gets a bit laggy/slow
4. Remove all images
5. Everything is fast and snappy again.

Expected behavior
History should probably have an image limit to prevent overloading the UI.

Desktop (please complete the following information):

• OS: Windows 10
• Browser: Firefox
• Commit revision 989a552

Additional context
Need more users to confirm this isn't just my end? My generated images reside on a SATA drive, main UI runs off an NVME.

[Rogal80]

I have same issue - SSD

[tiraua]

Can confirm, images on SSD

[kalkal11]

I concur.

Also is there a campaign to change the name of AUTOMATIC1111 Webui to Super Stable Diffusion or something? Some youtuber coined the term and now everyone is saying it

[mykeehu]

@AUTOMATIC1111 Can you use lazy loading for images? Don't load them all at once

[evanjs]

This should be mitigated with acedbe6

I should also note that I have not experienced any of these issues with the latest Gradio beta

This is likely because said release includes gradio-app/gradio#2265, which resolves some of the major performance issues relating to images.

[larinius]

@AUTOMATIC1111 Can you use lazy loading for images? Don't load them all at once

You asked for imposable hard to implement feature.
2024 year - same super slow loading ALL full size image in parallel. Maybe they shoud pay $5 on Fiver to some web dev to implement it