tags:

views:

278

answers:

3

When I measure request times on "the inside" of an Asp.Net application and compare it to timings on "the outside" of the app, I get different values -- 1000-5000ms strange overheads from time to time.

Maybe the requests are beeing queued up in front of IIS?

Or something strange is going on in an HttpModule?

The question: Is there a way to inspect the request pipeline for tracing exactly where the time is spent before the app is hit?

+1  A: 

You can create your own module and register it on top to trace every request with more accuracy, but the measure will start once the IIS delegates the request to the ASP.NET ISAPI module. To get more accuracy you can go to IIS logs.

Eduardo Campañó
A: 

You can turn on tracing in your web.config file. The line should say something like <trace enabled="true" pageOutput="true" />. The MSDN page is here.

Dan Goldstein
I know this one -- but I need info about stuff before the app is hit. Thanx anyhows :)
Christian Dalager
A: 
Vivek
Thanx - i've actually never used the trace.axd handler and it's a nice one! However as I need info about the pipeline before the app is hit, this doesn't help me.Besides - the portal im working on have duplicate controlIds (not mine..) so trace doesnt work.
Christian Dalager