Are you sure the server's load is 12 ? Or 12% ?
You have plenty of RAM... are you running under NT or Unix (I'm assuming UNIX).
What sort of Disk I/O subsystem are you using? You might be hitting an I/0 bottleneck on disk writes and reads.
Also, let's do a little math.
Mod_perl Apache is about 4 Meg per Unix process. (average). 200 processes running is 800 meg, plus the overhead control. MySQL is a 12-15 Meg process, that grows as it needs to. The more requests it's serving, and more tables it's got open, the more room it's going to require.
So, my point is that even with 1 GB of RAM, you might be running out of RAM, and doing a lot of disk swapping. If that's true, then we sort of go back to the previous I/0 problem.
You might be a candidate for dual-apache (proxy the mod_perl requests to a back end apache that's 4 Meg, but run 100 1 meg "light weight" servers to do the page serving). That could reclaim over half the RAM you are using with "fat" apache processes that are not actually processing CGI requests.
So, this begs the questions: What's your "swapfile" stats (how much are you using, and how much of your RAM is being used??
http://www.postcards.com
FAQ: http://www.postcards.com/FAQ/LinkSQL/
You have plenty of RAM... are you running under NT or Unix (I'm assuming UNIX).
What sort of Disk I/O subsystem are you using? You might be hitting an I/0 bottleneck on disk writes and reads.
Also, let's do a little math.
Mod_perl Apache is about 4 Meg per Unix process. (average). 200 processes running is 800 meg, plus the overhead control. MySQL is a 12-15 Meg process, that grows as it needs to. The more requests it's serving, and more tables it's got open, the more room it's going to require.
So, my point is that even with 1 GB of RAM, you might be running out of RAM, and doing a lot of disk swapping. If that's true, then we sort of go back to the previous I/0 problem.
You might be a candidate for dual-apache (proxy the mod_perl requests to a back end apache that's 4 Meg, but run 100 1 meg "light weight" servers to do the page serving). That could reclaim over half the RAM you are using with "fat" apache processes that are not actually processing CGI requests.
So, this begs the questions: What's your "swapfile" stats (how much are you using, and how much of your RAM is being used??
http://www.postcards.com
FAQ: http://www.postcards.com/FAQ/LinkSQL/
