Howard... got a thought here...
vBulletin initates it's scheduled tasks when people view the page (rather than via a cronjob). This is easier for setup but becomes a problem with you have 1000+ people on who all trigger the same update at once on 2 or 4 different web servers. People are moving faster than the database is getting updated so all the webservers "go" at the same time.
Why not kill the $cronjob variable (in the footer template) and set a true cronjob from one of the servers (maybe turn down that load priority too) so just one is handling all of the email alerts, threads notices, etc.
You may have done this long ago, just an idea.
vBulletin initates it's scheduled tasks when people view the page (rather than via a cronjob). This is easier for setup but becomes a problem with you have 1000+ people on who all trigger the same update at once on 2 or 4 different web servers. People are moving faster than the database is getting updated so all the webservers "go" at the same time.
Why not kill the $cronjob variable (in the footer template) and set a true cronjob from one of the servers (maybe turn down that load priority too) so just one is handling all of the email alerts, threads notices, etc.
You may have done this long ago, just an idea.
Last edited: