Don’t run production ASP.NET Applications with debug=”true” enabled
Don’t run production ASP.NET Applications with debug=”true” enabled.
Doing so causes a number of non-optimal things to happen including:
1) The compilation of ASP.NET pages takes longer (since some batch optimizations are disabled)
2) Code can execute slower (since some additional debug paths are enabled)
3) Much more memory is used within the application at runtime
4) Scripts and images downloaded from the WebResources.axd handler are not cached
…….
The override:
<configuration>
<system.web>
<deployment retail=”true”/>
</system.web>
</configuration>
———————————————————————————
Really good pointer on disabling debug on ASP.NET compiliation so there is no unecessary PDB file generation.
Today my hosting serve went down because it ran out of disk space on the C: drive. Turns out, all my sites have the element <compilation debug=”true” /> option set. So, if I have it set, good chance most other sites on the shared box have it set.
So, PDB files are being generated, but never used. These files can be 5x size of the generated DLL’s.