
|
View Full Version : Why would a restart speed things up?
My server was working fine, then all of a sudden things started to get very slow. This lasted for a few hours. Traceroutes from dozens of locations all over the US looked good. The one traceroute that was bad was from my Windows 2000 computer. There was a big delay on the last couple hops, right at the server. I restarted the server, and suddenly everything was fast again.
This situation does not make any sense to me. If the problem was at the server end, why would the traceroute from my computer be the only one with a problem? If the problem was on my end, then why would a server restart correct it?
Can anyone explain this situation? Note that it had been less than 2 days before the previous restart.
bobcares 12-19-2001, 08:25 AM Welcome to the wonderful world of microsoft where most of the answers are left to your imagination..... :)
microsol 12-19-2001, 09:30 AM Originally posted by NVB
There was a big delay on the last couple hops, right at the server. I restarted the server, and suddenly everything was fast again.
:eek: You say that the traceroutes are fine from different locations! Why would you restart the server if this problem is clearly on your site? Try to restart your winblowz machine BEFORE you take any other action! :eek:
RackMy.com 12-19-2001, 10:16 AM My server was working fine, then all of a sudden things started to get very slow. Can you open up the task manager and see what is going on. Your issue is probably not network related, but IIS chewing up CPU or memory. Can you give us more information?
I believe I have confused some people with my original post. My server uses Linux with Apache. My home computer uses Windows 2000.
Everything was speeding along at my site on the server, then I left for under one hour. When I returned things became very slow. Traceroutes from a command shell from my home computer using the command tracert consistently showed big delays on the last hops, at the server (not at the home computer). Traceroutes from other locations all appeared fine. Restarting the home comuter did not have any effect, but restarting the server corrected the problem.
I am not familiar with task manager for Linux. Top shows the following. The numbers were similar last night, but there was a larger server load since I get more visitors during prime time than during the morning (its 7:30AM here in PST).
11:32am up 48 days, 14:54, 1 user, load average: 0.00, 0.08, 0.08
50 processes: 48 sleeping, 1 running, 1 zombie, 0 stopped
CPU states: 4.1% user, 0.9% system, 0.0% nice, 94.8% idle
Mem: 509272K av, 303068K used, 206204K free, 72912K shrd, 141088K buff
Swap: 530104K av, 0K used, 530104K free 125480K cached
microsol 12-19-2001, 11:45 AM Originally posted by NVB
I am not familiar with task manager. Top shows the following. The numbers were similar last night, but there was a larger server load since I get more visitors during prime time than during the morning (its 7:30AM here in PST).
11:32am up 48 days, 14:54, 1 user, load average: 0.00, 0.08, 0.08
50 processes: 48 sleeping, 1 running, 1 zombie, 0 stopped
CPU states: 4.1% user, 0.9% system, 0.0% nice, 94.8% idle
Mem: 509272K av, 303068K used, 206204K free, 72912K shrd, 141088K buff
Swap: 530104K av, 0K used, 530104K free 125480K cached
There's nothing wrong with this.
|