Server type question

[FATPad]

When you telnet in to a server (or ssh1 or whatever) and do a TOP command you get 3 numbers next to "load average".

I know the higher the numbers, the heavier the server load is, but what exactly do they mean?

[ServerGenius]

Not 100% sure but to my knowledge it displays the average
system load over the last 1.5 min, 15 minutes, 15 hours

correct me if I'm wrong

DynaMite

[darksoul]

its over the last 1,5,15 minutes
and you get the same thing if you use "uptime"

[ServerGenius]

Thanks darksoul...I was close hehehe

DynaMite

[buran]

Since I'm too late to answer this question, lemme throw in some other useful tricks

aaron@loadtime1:~> ps -aux | grep httpd | wc -l
44

This will show you the number of HTTP children running

aaron@loadtime1:~> netstat -an

This returns a list of all the network connections to your server at that moment.

File these away and someday they might come in handy.

[ServerGenius]

Buran please contact me asap either on ICQ 370820 or by
email [email protected]

Thanks

DynaMite

[FATPad]

If anyone is really familiar with this stuff and has a couple of mins to answer a few questions, I'd appreciate it. ICQ 44737242. Something whacked is going on on one of my friends servers and I have a few questions.

Thanks.

[FATPad]

All set. Got some answers now. Thanks.

[salsbury]

secrets(not really) to httpd happiness:

keepalive off
startservers 512
maxclients 512
maxspareservers 3
minspareservers 2
maxrequestsperchild 100 # *

the goal of this is to have the machine never swap. swap, while necessary, should almost never ever ever be used by a web server - especially one running scripts - it'll send it in to a downward spiral.

these variables will make apache start up using the minimum amount of memory it ever will. the maxrequestsperchild is low just in case there are any memory leaks anywhere. it's not bad to have it this low, btw. say your server is doing only around 50 hits per second (i know slow day ). that's 1024 seconds before a child needs to die, at least. any server can handle this no problem.

these config options made no difference in every day server performance, but since they were put in to place over 1 year ago on the servers i administer, most have had NO swap problems at all, and the ones that did were due to pathological problems that can't be easily prevented (but are easily solved of course. )

i type too much.

[darksoul]

Originally posted by buran
Since I'm too late to answer this question, lemme throw in some other useful tricks

aaron@loadtime1:~> ps -aux | grep httpd | wc -l
44

This will show you the number of HTTP children running

admin#~ ps aux|grep -c httpd
does the same thing

[i][
aaron@loadtime1:~> netstat -an

This returns a list of all the network connections to your server at that moment.

File these away and someday they might come in handy. [/B]

since we're talking
about apache you better use
netstat -an|grep 80
as well as apachectl fullstatus