I have a quick query relating to the notification functionality in myAlbum-P. When a user submits a new image it appears that notifications are fulfilled in real time. So if I have 10,000 users who all have PM notifications for any new image it is going to have to generate all 10,000 PMs in that one page request. Am I correct in thinking this?

We are having serious performance problems with our XOOPS / myAlbum-P install and I think it is due to the notifications. Currently we have about 260,000 images (+ 2000 / day) and 10,000 users and it seems to be grinding to a halt.

TIA

Notifications of myAlbum-P will occur just in posting stage.
Thus, I guess the feature is not the reason why your site is heavy.

If you don't want users use the notifications, just disable it.

Thanks for your reply. I just wanted to sanity check my understanding of the code having only had a quick look.

There are times when a user posts a message and the notifications code generates and executes upto 3,000 queries. Thinking this to be the cause of the performance issues I disabled notifications and put some timers into the submit script to try to find the bottleneck. The logging from the submit script did not provide any consistent results.

I have also created some scripts that profile the MySQL server using the SUPER privilege, to make sure it can always connect. When the webserver comes to a grinding halt there is always a SELECT query executing against the "xoops_myalbum_photos" table with a large number of INSERT queries being queued behind it.

It is the MySQL server that is becoming completely locked up. When I connect it can take up to a minute to get the MySQL command prompt returned. Executing "SHOW FULL PROCESSLIST" can take up to ten minutes to return.

Any thoughts or suggestions would be very much appreciated.

hmmm.
If it is just a problem of number of SELECT queries, fastest cache hack (FCH) can be help you.

But even FCH cannot help about INSERT queries.

All I can say "move into powerful server", sorry.