OH! You're running Apache. Why didn't you say so?
Can I also assume that the Apache processes are the clients of Mysql?
You can throttle back Apache to prevent a system crash much easier than you
can throttle Mysql (IMHO).
Use a line like this in Apache's httpd.conf file:
MaxClients 50
This will limit the number of apache (httpd) processes and thus keep your
memory usage and load under control.
User of the web site may have slower page load times, but the system will
not crash.
You can of course try increasing the number, maybe 100 would work better
for you.
Have you looked at memory usage when your system is at "100% CPU" (I don't
even know what 100% CPU means, personally). I used to have problems with
my system running out of memory, it would start to "page its brains out"
and eventually the system would crash. MaxClients solved that problem for me.
I'm using mod_perl though, and my httpds have a large memory footprint, so
maybe this solution only applies well to that case.
-bill
At 08:33 AM 3/20/2001 +0000, you wrote:
>hi,
> i've not reconfigured linuxthreads.
>/proc/sys/kernel/threads-max has 57344. At the time
>when the machine hits 100% CPU, apache processes are
>taking most of the CPU time, and i have around 250
>processes on the entire system, with around 10-15
>running processes. mysqladmin status shows me around
>15 mysql threads running. Agreed that something like
>this should not happen, the CPU touching 100% is not
>an acceptable situation, but what i'm worried abt is
>mysql crashing. If the OS goes for a toss, i know
>that it is a problem with the load, but mysql is
>getting something like a 100-150 queries at that time.
---------------------------------------------------------------------
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
