CLR Memory

[MSFT Developer]

We are running into a problem where the SQL server and the webservers goes
to a state where all the queries that normally return results in less than 3
seconds takes more than a minute or two. So far the only way we could get
around this is to reset SQL server. Recently we found that even this doesn't
help. We need to reset both SQL and IIS server. Can you point me in the
right direction what are the things I should look at.

The configurations are:

SQL Server: WIN 2K, 4 GB RAM, 4 processor
Web Server: WIN 2K, 2GB RAM, 2 processor, IIS 5.0, dot net 1.1. These
servers are connected via load balancer but sticky is used to maintain
session. 40% memory is allocated to asp.net on each of the machines. We
don't use web garden.

One thing I noticed is, Even though the web servers are identical in
configuration in the perfomance monitor I noticed that the ".NET CLR
memory - # Total Reserved Bytes" on one machine is twice the size as the
other machine. When I looked at the Task Manager on both the machines the
machine that has 1/2 the amount of reserved bytes shows only once CPU Usage
History, whereas the other machine shows two CPU Usage History. Does this
give any clue why the reserved bytes are 1/2 size on one machine than the
other server?

Also when I looked at the SQL Server thread count it is about 250. Is this
something I should be concerned about?

Let me know your thoughts.

Thanks in advance.

 

[MSFT Developer]

While reviewing the IIS log I noticed that few pages that return the status
(sc-status) 200 at some point throws error status 500. That is the time the
web server, SQL server is taking long time to display pages. Eventually
causes to reset IIS and SQL server.

What could be the reason the pages throw error 500? But once the IIS is
reset the same pages returns status 200.