On Fri, Mar 09, 2012 at 09:07:34AM +0100, Simone Frattegiani wrote: > > Server-status shows this: > > Total Accesses: 292068 > Total kBytes: 5540956 > CPULoad: .0884054 > Uptime: 45823 > ReqPerSec: 6.37383 > BytesPerSec: 123823 > BytesPerReq: 19426.8 > BusyWorkers: 99 > IdleWorkers: 10 > Scoreboard: WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW > WWWWWWWWWWWWWWWWWWWWWWWWWWKWWWWWCWWWWWWWWWKWWWWWWWWWWKWWW_W_CWWW__WS__K_WWK__K_S........ > ........................................................ > ................................................... > > With hundreds of lines like this (66.249.66.44 is googlebot): > > 24-0 - 0/0/8 . 0.02 661 34 0.0 0.00 0.00 66.249.66.44 > www.mydomain.com GET /mypage > > So, please correct me if i'm wrong, that 661 in the SS column means > that 661 seconds have passed since the last time Googlebot used that > slot to make a request... That is correct. > so basically the server is keeping alive a > connection that has been idle for like 11 minutes!! That is incorrect. The hyphen in the second field indicates that there is no running process associated with this slot. Furthermore the dot in the status collumn indicates that it is an empty slot (look at the Scoreboard Key for meanings of characters in the status column). > Did i understand correctly? Is it normal? Is it what is causing the problem? It is normal, so that's not anything to worry about. The problem is more likely to be connected with the surprisingly large proportion of your slots in the W status. When the problem occurs, check to see what those W status processes are doing (also check you error log, of course). HTH, Pete -- Openstrike - improving business through open source http://www.openstrike.co.uk/ or call 01722 770036 / 07092 020107
Attachment:
pgpYLesc2pqYM.pgp
Description: PGP signature
|