Performance hit on ASP.NET

[Jeremy]

I'm seeing a huge performance decrease in my ASP.NET
pages when executing on a production machine verses my
local machine. It isn't the bandwidth, and it isn't the
code itself. For some reason the compilation, or caching
or something is destroying the response times. While it
executes perfectly locally (XP & IIS 5) it executes
periodically at about 45 seconds or more per page on the
production machine (2000 Server & IIS 5). Any ideas?

 

[Todd Thompson]

I would suggest editing the web.config file <trace> tag and enable it and
enable the pageOutput attribute. You can then create a trace context and
output to it.

protected System.Web.TraceContext con = null;

protected void PageLoad()
{
con = this.Page.Trace;
con.Write("PageLoad", "_Begin something");
// doing something
con.Write("PageLoad","_End something");
}

It provided me some very valuable timing information that helped me isolate
the source of a slowness I was experiencing, namely using the
identity.IsInRole(group) function.

HTH,

Todd Thompson

 

[Jeremy]

I have timers set on each section of the code, including
the constructor, the pageLoad and the executions... they
all execute in effectively zero time, somewhere IIS is
simply locking up for up to a minute at a time, probably
prior to ever executing the page.