Hi, John.
There's a bit more information at
http://msdn.microsoft.com/library/de...netchapt06.asp
and it sheds a bit more light on this.
---000---
Ensure Debug Is Set to False
When debug is set to true, the following occurs:
Pages are not batch compiled.
Pages do not time out.
When a problem occurs, such as a problem with a Web service call,
the Web server may start to queue requests and stop responding.
Additional files are generated in the Temporary ASP.NET Files folder.
The System.Diagnostics.DebuggableAttribute attribute is added to
generated code. This causes the CLR to track extra information
about generated code, and it also disables certain optimizations.
Before you run performance tests and before you move your
application into production, be sure that debug is set to false
in the Web.config file and at the page level.
By default, debug is set to false at the page level. If you do need
to set this attribute during development time, it is recommended
that you set it at the Web.config file level, as follows :
<compilation debug="false" ... />
The following shows how to set debug to false at the page level.
<%@ Page debug="false" ... %>
Note A common pitfall is to set this attribute at the page level
during development and then forget to set it back when the
application is moved to production.
---000---
A good way to establish whether there's a "degradation",
or a "big hit", is to build a Debug version and a Release version
of any application and profile both with the Web Application Stress Tool :
http://support.microsoft.com/default...b;en-us;815161
Download the WAST from:
http://www.microsoft.com/downloads/d...displaylang=en
WAST does run on Windows Server 2003 *and* Windows XP,
even though they are not mentioned in that page.
The IIS Resource Kit Tools also has a neat tool called the
"Web Capacity Analysis Tool" (Version 5.2) which can also
be used to see how much of a performance hit exists in Debug
versions of ASP.NET apps, compared to Release versions.
Get it at :
http://www.microsoft.com/downloads/d...DisplayLang=en
Juan T. Llibre
===========
"John Saunders" <johnwsaundersiii at hotmail.com> wrote in message
news:OP**************@TK2MSFTNGP14.phx.gbl...
"Juan T. Llibre" <no***********@nowhere.com> wrote in message
news:uc**************@TK2MSFTNGP10.phx.gbl... re: Can you point me to some documentation that says this?
I don't remember ever seeing it.
http://samples.gotdotnet.com/quickst...erftuning.aspx
15. Do not forget to disable Debug mode: The <compilation> section
in ASP.NET configuration controls whether an application is compiled
in Debug mode, or not.
Debug mode degrades performance significantly. Always remember
to disable Debug mode before you deploy a production application
or measure performance.
Thanks. I see there's a language issue. "significantly" != "big hit" to
me.
John Saunders