If you have too many photos (in our specific case, that's 52k photos in sub-albums), the "new" algorithm to detect how many photos would become orphans if we delete the album. Indeed Piwigo sends the full list of image_ids associated to the album (and sub-albums).
In my current case, the SQL query takes 78 seconds and simply leads to Gateway Timeoutin nginx.
If you have too many photos (in our specific case, that's 52k photos in sub-albums), the "new" algorithm to detect how many photos would become orphans if we delete the album. Indeed Piwigo sends the full list of image_ids associated to the album (and sub-albums).
In my current case, the SQL query takes 78 seconds and simply leads to `Gateway Timeout`in nginx.
<!-- github-sync-id:403756743 -->
adam
changed title from [albums] performance issue on edition page, when too many photos to [albums] performance issue on edition page, when too many photos 2026-10-27 11:12:52 +01:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
If you have too many photos (in our specific case, that's 52k photos in sub-albums), the "new" algorithm to detect how many photos would become orphans if we delete the album. Indeed Piwigo sends the full list of image_ids associated to the album (and sub-albums).
In my current case, the SQL query takes 78 seconds and simply leads to
Gateway Timeoutin nginx.[albums] performance issue on edition page, when too many photosto [albums] performance issue on edition page, when too many photos