More and more frequently I encounter a major performance issue with Piwigo when combining these conditions:
many photos/albums, like 100k photos and 1k albums
private albums or photos
photos are being uploaded with web upload or API
each photo is uploaded in a few seconds (small photos or big bandwidth)
visitors are active on gallery side
My current researches goes to a "lounge" where photos are added (bufferized) before being really added to their actual albums.
Related to problem described on https://piwigo.org/forum/viewtopic.php?id=28338
> More and more frequently I encounter a major performance issue with Piwigo when combining these conditions:
>
> * many photos/albums, like 100k photos and 1k albums
> * private albums or photos
> * photos are being uploaded with web upload or API
> * each photo is uploaded in a few seconds (small photos or big bandwidth)
> * visitors are active on gallery side
My current researches goes to a "lounge" where photos are added (bufferized) before being really added to their actual albums.
<!-- github-sync-id:904952235 -->
Very related to #1367 but not exactly the same (both can be implemented separately and both will improve performances)
Very related to #1367 but not exactly the same (both can be implemented separately and both will improve performances)
<!-- github-comment-id:850252429 -->
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.
Related to problem described on https://piwigo.org/forum/viewtopic.php?id=28338
My current researches goes to a "lounge" where photos are added (bufferized) before being really added to their actual albums.
Very related to #1367 but not exactly the same (both can be implemented separately and both will improve performances)