You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Change or disable the client-side processing of an image group so that large groups of images don't make the application unresponsive for long periods of time when the first image in that group is clicked. #752
[Preface: I assume the "client side processing" I'm referring to below is just PiGallery loading images and videos into a local cache. But since I don't know what it's really doing, I just called it "Processing."]
PiGallery is doing some kind of processing to every image in a grouping when the first thumbnail of that grouping is clicked. In large libraries, this can make the application unresponsive for a very long period of time until that processing is completed. One group with over 1700 images took over 30 seconds to load the first image clicked on, during which time the web browser is using as much processing time as it can. Larger grouping methods (such as choosing "no group") take so long to complete this processing that the web browser will present a message (in Safari) saying that the page has stopped responding and must be force-reloaded. This effectively makes PiGallery 2 unusable for very large image libraries.
Note that it works great if the grouping has very few images. When grouping by rating, for example, I have very few images with ratings, so all of those images load rapidly and work just like they did in previous versions of PiGallery. But the moment I click on an image in the "no rating" group, the client-side processing begins and I have no hope of it ever finishing in my lifetime, it seems.
Instead of the client-side processing for every image in the group, could that perhaps be limited to just the image being clicked on or loaded by a slideshow? Or provide an option to turn off this processing (whatever it is) in the admin panel?
I would really love to use the features in 2.0.0, but it is effectively unusable for my library. I did try the edge version and a few other versions, as well as a full install on a different host, but always ran into this issue. All devices are connected to each other (including image storage) via gigabit ethernet.