F
Fredrik Melin
We have a larger ASP.NET application that is running on 3 identical servers,
(Network Load balanced) with Windows 2003
On average the servers has 250 active sessions each. They serve about the
same number of requests per second.
Now, after running for sometime, we are loosing processor time, (avg %
processor time for the asp.net) is slowly rising, and after a while (days)
the processor queue length gets higher and higher, and finally the server
will stop serving requests.
We reboot the server automatically, and its back to zero again, starting to
climb.
We cant see any obvious errors in the application it self, neither does eat
up the memory. Its just affecting processor performance.
Any tips?
Regards
Fredrik Melin
(Network Load balanced) with Windows 2003
On average the servers has 250 active sessions each. They serve about the
same number of requests per second.
Now, after running for sometime, we are loosing processor time, (avg %
processor time for the asp.net) is slowly rising, and after a while (days)
the processor queue length gets higher and higher, and finally the server
will stop serving requests.
We reboot the server automatically, and its back to zero again, starting to
climb.
We cant see any obvious errors in the application it self, neither does eat
up the memory. Its just affecting processor performance.
Any tips?
Regards
Fredrik Melin