On Fri, 09 Jan 2004 09:04:14 +0000, Davide Bianchi wrote:
> Stefano <c-t-b-k RemoveThis @gmx.it> wrote:
>> Connecting via ssh to the server and downloading a gif with the
>> command: wget <a style='text-decoration: underline;' href="http://localhost/img/testimg.gif" target="_blank">http://localhost/img/testimg.gif</a> takes ages to complete.
>
> Whit so less information it's hard to tell what can be the problem.
> If you have the status enabled in the server ask the status and check
> if there are a lot of request pending or something, check the log
> files for unusual things, try to find out if there is a problem is
> establishing the connection or a problem in the actual processing.
> Check the memory usage and eventually the swap space used.
just before the hourly shutdown-restart the server was slow (but not
stuck), and this was the situation:
free:
total used free shared buffers cached
Mem: 2069020 2016360 52660 0 12588 1413312
-/+ buffers/cache: 590460 1478560
Swap: 979956 6744 973212
server-status:
Current Time: Friday, 09-Jan-2004 16:54:10 CET
Restart Time: Friday, 09-Jan-2004 16:00:33 CET
Parent Server Generation: 0
Server uptime: 53 minutes 37 seconds
Total accesses: 317189 - Total Traffic: 699.5 MB
CPU Usage: u186.77 s34.87 cu.56 cs.33 - 6.92% CPU load
98.6 requests/sec - 222.6 kB/second - 2312 B/request
512 requests currently being processed, 0 idle servers
RRRRKKRKWKKKRRRRRRKRRRWRRKKRRRRRKRRRRRKRRRRRRRWRRRRKRWRRRRRRRKRR
RRRRRRRRRRRRRRRKRKRRRRRRRKKKKRKRRKWRKRKRRRRKRWRKRRRRRRWRRRRRRRRR
RRKRWRRRRRRWRKRRRKRKRKKRRWKRKRRRRRKKKKRKRRRWRRKRKRRRKRRRRRWRRWRW
KRRRKRWRKKRRWRKRRRRKRWRKRRKRRRRKRRRRRRRRRWWRRRKWRRWKRKRWKKRWRRRW
WWRRKRRKWKRKRKRKRKKRRWRRRRRWRRRRKRRRRRRKRRKWRWKRKKRRRRKRKWRRRRRK
KRRKRWKRKWKRRRKKRKKRKWKRRRRWRWKKRRKRRRRRKRWKKRRWKWRKRRRRRKRKRRRR
RKWRRRRRRRRKWRRWRRKRRKKWRRWKRRKRRRRRRRRKRRRRRRRRRRRRRRRRRRKRRKRK
RRKKWRRKRRKRRRRKKWWRWWRRKKRRKWKKKWRRWWKRRRKKWKWRRWRRRKWRRRRRRKKR
0 idle servers, and a lot of Rs here, meaning "reeading requests".
server-status says 98.6 req/sec, but apachetop, running at the same
moment said 50 req/sec;
I'm puzzled. Right after the restart memory occupation was more or less
the same, but server status was quite different:
Server Version: Apache/1.3.29 (Debian GNU/Linux) mod_gzip/1.3.26.1a PHP/4.3.3
Server Built: Dec 17 2003 15:54:05
Current Time: Friday, 09-Jan-2004 17:04:32 CET
Restart Time: Friday, 09-Jan-2004 17:00:34 CET
Parent Server Generation: 0
Server uptime: 3 minutes 58 seconds
Total accesses: 24172 - Total Traffic: 53.0 MB
CPU Usage: u15.18 s3.06 cu.06 cs.03 - 7.7% CPU load
102 requests/sec - 228.1 kB/second - 2299 B/request
172 requests currently being processed, 52 idle servers
_KKRRKKRRKK_KKKKRKKK_K__WRKRKRRKR__KK_RKRKKKK_KKK_KRKKK_RKK_KK_K
___K_RKWKKK_K_K_KKKKW__KRW_WW_WKRKKRKKRKKWKKKK__K___KWKK___K_KKK
WKKKKKKK_W_R_KKKWRKKKK___KWRK_RKK_KKK_KKKKKKK__WK_KKRKKKKKKKKKKK
KK_K_K__KKKKRKKKKKKK_KKKKKK_K_KK................................
Very few Rs, and the site is blazing fast.
102 req/sec now is the same data I get with apachetop: 102-105 req/sec
Any idea?
Thanx
S
--
<a style='text-decoration: underline;' href="http://grok.splinder.it" target="_blank">http://grok.splinder.it</a>
se vuoi scrivermi togli i trattini dall'indirizzo<!-- ~MESSAGE_AFTER~ -->
>> Stay informed about: After a while, apache gets slow without any cause