OK - - thanks for your help. Unfortunately, this is still a bug... " PhotoPost is only as good as your PHP and MYSQL setup and limited by its limits" doesn't really answer my question.
We've done all of the suggested changes. We have the latest PHP and the latest MYSQL. We are running in a HA clustered environment with the top hardware money can buy. The problem is with photopost. Our PHP and MYSQL seem to be perfect for Fusionbb, UBBthreads, and a whole host of other softwares running at VERY high levels. Photopost is the only one of the bunch that just can't handle the traffic.
As confirmed by your link and post, photopost may not be built to handle sites with more than 100K images or with high volumes of traffic. This is unfortunate, since we feel like Photopost is one of the reasons we were able to grow so large...
We are running into all kinds of problems now....
images are showing up under the wrong users (happened in the past, happening much more often now), SLOW page loads, MYSQL locking up only photopost dbase locks up (all others on the servers are totally fine).
I have figured out what one of the problems is. If you are an admin and you click "upload photos", it loads ALL of every users albums in the album drop down. This is problematic. We have over 5000 user albums. Where is the admin setting to turn this off? Or is there a simple hack so that we can turn this off?
This one query locks up photopost dtabase nearly every time.