Task #61588
closed
Loading many images in backend forms is slow
Added by Kay Strobach about 10 years ago.
Updated over 4 years ago.
Category:
Backend User Interface
Description
What i've done:
- upgraded an installation from 4.5 -> 4.7 -> 6.1 -> 6.2
What i've expected:
What i got:
- For some tce_forms and backend moduls i need to wait up to 5 minutes to load
Steps to reproduce (way 1 listmodule):
- create a page
- add text w/ image elements
- add quite an amount of images (20-50)
- clean the corresponding processed folder (as it would be after the update)
- try to open list module of the page with preview enabled
Steps to reproduce (way 1 tce_forms):
- create a page
- add text w/ image elements
- add quite an amount of images (20-50)
- clean the corresponding processed folder (as it would be after the update)
- disabled image preview in user settings
- open list module try to edit the created content elements, also takes quite long
Ideas for a solution:
I really like the direct embedding of the images, but speed matters more, so i would suggest the following:
1. try to render previews and store them
2. track time, and if it takes longer then 2 or 3 seconds fallback to thumbs.php and create the images in parallel after loading the module
Another solution would be to show some kind of progressbar as the number of images should be known somehow ;) (but i like the soft fallback with more speed much more!)
this would have several positive effects on the felt speed of the TYPO3 Backend.
I would prefer a delayed rendering of all thumb images. IMHO it is absolutely fine to just reserve the space for the images and fill them in later. That way the page will be fast and the images can be loaded later on.
I will need to consult with a frontend expert on how to implement the CSS/JS in a clever way, but a delayed fetching of thumbs is the way to go here.
as the space is already fit, good old thumbs.php is the way to go :D
- Subject changed from Module Loading slows down dramatically to Loading many images in backend forms is slow
- Complexity set to easy
Thanks for this report, I changed the subject to a more precise one
- Status changed from New to Accepted
- Complexity changed from easy to medium
I could not reproduce the thingy with not having a "good usable backend" as you wrote above.
However, I agree that form rendering can be decoupled from image pre-processing and rendering.
Besides that, the pre-processing still might have some room for improvements - did anyone had a chance yet to profile that further?
@Kay Wienöbst This issue is about the first hit, when files have not been processed yet, right? After second hit, everything is fine?
partially right.
- the first hit is the one with the biggest impact (if all images could be resized), but if you have many images on a page, it may take quite a lot longer than this first hit and due to time outs i needed often more than one hit ...
- If you have many images on a page, it can still take noticeable longer on the second hit, due to the DB requests.
So my suggestion is to have a image rendering timer, which counts the time the VH etc. need and if a defined value (e.g. 10s) is exceeded create links to sth. like thumb.php with signed parts in the uri to speed up the reaction (this can also be used in the frontend IMHO). If image is created in the thumbs.php make a redirect (location changed) to the correct location.
Imagine the upload times, if you use slow remote storages ...
- Target version changed from next-patchlevel to 7.4 (Backend)
- Target version changed from 7.4 (Backend) to 7.5
- Target version changed from 7.5 to 7 LTS
- Tracker changed from Bug to Task
- Target version deleted (
7 LTS)
- Related to Feature #60835: Slow manipulation of file relations in backend user interface added
- Related to Feature #59341: Provide progress indicator while image-processing FAL uploads added
- Status changed from Accepted to Needs Feedback
Care to test this again with master / v9? There have been some changes to rendering / processing images async which should help mitigate the issue.
- Status changed from Needs Feedback to Closed
No feedback for a long time, cannot reproduce the issue, closing.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by