It may be that MySQL is simply spawning too many processes for your
machine to handle.
I might be wrong, but here's something to try:
1. Set MySQL max_connections to 45.
2. Set httpd MaxClients to 50.
That will limit the number of processes MySQL is allowed to start, and
also makes sure that Apache will delay web requests such that it won't try
to service a request when MySQL is at the maximum number of processes.
This may keep your machine from spinning out of control. However, there
might be a bug somewhere that's making MySQL take up more system resources
than it should, and my solution does not address that possibility. Maybe
someone else has an idea about this.
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
