If you leave <compilation debug=”true”/> switch on within the application’s web.config file in production it will effect performance of the application.
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
Subscribe to:
Post Comments (Atom)
LIveCharts2: Charts for Windows and web
Charts for Windows and web including .Net MAUI LiveCharts - LiveCharts2 (lvcharts.com)
-
HttpClient is a .NET class that an app can use to send HTTP requests and receive HTTP responses from a REST web service. The resources that...
-
Label tb = new Label (); tb.Name = "LabelID" + iRow; tb.Content = lblName; Grid .SetColumn(tb, iCol); Grid .SetRow(tb,...
-
Grid is a layout panel that consists of rows and columns. Example 1: < Grid > < Grid.RowDefinitions > < Row...
No comments:
Post a Comment