Measuring debug vs release of ASP.NET applications

Posted by Alex Angas on Stack Overflow See other posts from Stack Overflow or by Alex Angas
Published on 2010-05-11T04:11:12Z Indexed on 2010/05/11 4:14 UTC
Read the original article Hit count: 220

A question at work came up about building ASP.NET applications in release vs debug mode. When researching further (particularly on SO), general advice is that setting <compilation debug="true"> in web.config has a much bigger impact.

Has anyone done any testing to get some actual numbers about this?

Here's the sort of information I'm looking for (which may give away my experience with testing such things):

Execution time     | Debug build   | Release build
-------------------+---------------+---------------
Debug web.config   | average 1     | average 2
Retail web.config  | average 3     | average 4


Max memory usage   | Debug build   | Release build
-------------------+---------------+---------------
Debug web.config   | average 1     | average 2
Retail web.config  | average 3     | average 4


Output file size   | Debug build   | Release build
-------------------+---------------+---------------
                   | size    1     | size 2

© Stack Overflow or respective owner

Related posts about ASP.NET

Related posts about testing