Geek Answers Handbook

ASP.NET application crashes on light load in IIS 7. Requires a timeout. How to debug?

We have an ASP.NET site that runs on IIS7 in Windows Server 2008 - in fact, we run the same code on several identical servers. Traffic is growing, and sometimes, in higher traffic, the site (actually the application) becomes unresponsive - or at least so slow that it seems unresponsive. The only thing to do is stop / start W3SVC; Recycling the site or application does not fix it.

The same symptoms occur (sometimes, and seemingly by accident) on several servers. So this is not a specific box. These servers have 8 GB of RAM and do not use more than 5 GB; and CPU usage averages around 40-50% even during these high-traffic periods. So this is hardly a problem.

There are no application errors or basic timeouts (SQL, etc.), and nothing is written to the event log. Usually, when we look at ASP.NET in PerfMon, requests run around 5-10 and requests run around 25-40. When it starts, these numbers constantly grow to infinity, as each request expires for the client.

Although I would like a silver bullet, I mostly hope for a better approach to debugging things. Are there any better PerfMon rooms? Something you can register? Something to try or check?

Thanks in advance for your ideas, hive-mind!

+4
source share
1 answer

Tess Ferranddes has an excellent series of publications / laboratories on how to debug such problems:

.NET Debugging Demos - setup and configuration instructions

Unfortunately, rarely there is one solution for a bullet with silver for such problems. You need to get a dump of this workflow when it freezes, and then start thinking about how to use WinDBG and SOS.

+1
source

More articles:


All Articles