Tips to Improve the Performance of ASP.Net Application

Dinesh Tawar

.NET performanceHow to improve performance of asp.net Applicationperformance of ASP.Net Applicationperformance tips

11 Comments

Join the conversation! Your thoughts help the community grow.

Mukesh Kumar11y ago
Very helpful for my site
fredrick james16y ago
ASP.NET cache is good for improving performance but keep in mind its problems too. ASP.NET cache is a single point of failure, gives you data integrity problems in Web farms/garden. It has cache size limit, too. If you want to avoid these problems, the only option is to use third-party distributed cache. There are a few available for free like <a href="http://www.alachisoft.com/download.html> NCache Express </a>. One of the good things i found in this software is that it requires no code change in ASP.NET at all.
Amit Pathak19y ago
Your tips are nice, I want to confirm that which reporting tool should i use for reporting using asp.net (c#), sql server2000, Crystal report i think it Takes more time,resource. Suggest me
Ritu Dhiman20y ago
hi i m facing an unusual problem while developing asp.net application with vb.net as code behind. i m using tabstrip with multipage control.their are 5 tabstrip objects having 5 different datagrids on each one of 5 pageviews. some validations are also done on each of them like textboxes within datagrids shud be integer ,while cliking add button no field sgud be empty in footer template etc.now the problem is i m using editcommand column within datagrid. all buttons like edit,cancel,add delete are working except update button.when i click on update button neither this event {Public Sub DgrdTreasury_UpdateCommand(ByVal source As Object, ByVal e As System.Web.UI.WebControls.DataGridCommandEventArgs) Handles DgrdTreasury.UpdateCommand} and nor this{ Public Sub DgrdTreasury_ItemCommand(ByVal source As Object, ByVal e As System.Web.UI.WebControls.DataGridCommandEventArgs) Handles DgrdTreasury.ItemCommand} fires means nothing happens. what i guess is this is because when i click update button it starts validation of all the datagrids because they r placed on same page but in different pageviews.now if wat i guess is true then how to set causevalidation as false in editcommand column as their is no builtin property like causevalidation. wat shud i do please suggest
- ahmed arbab19y ago
  hi befor months i was face same problem, i think the soultion was, the tabstrip have event onchange tabstrip on code behid try to stop all other tabs casevalidation except the current tab programmaticly the diffrancess between tabs known be checking the current tab index sorry for i am arabic spoken
- Dinesh Tawar20y agoedited
  hi ritu, i am sending some code just try this code and let me know its working or not. in html view of your page put this. <asp:Datagrid id ="dgupdate" onUpdateCommand ="datagrid_UpdateCommand" & rest of tags > datagrid_UpdateCommand - is the event name of your datagrid control try this and let me know . dinesh
Hima Bindu20y ago
If we use HTML Controls instead of Server controls which in turn my enhance the performance Go for server controls only when it's really necessary
- Hima Bindu20y ago
  It's only one of the point to improve the performance of the application It's(using HTML) will not effect the 100% performance
- Dinesh Tawar20y ago
  hi hima, its nice to see your comment, the control is one entity for performance and other things also affects the performance. i think 40% is controls which we used in our application and other 60% is the other factors ( like connection string , use of dataset, datareader , debug option etc.) bye Dinesh
Simple Man20y ago
Dinesh, This site has the same article but it was posted there in March. http://www.codeproject.com/useritems/NET_Tips_and_tricks.asp .NET Performance Tips & Tricks By arunlala
- Dinesh Tawar20y ago
  All points are in details and how it affects performance

1. Disable the Debug Mode or Set Debug ="false"

How it affect performance: By default this attribute is "true" when you create new application and is useful when you are developing the application. Debug = true means that pdb information to be inserted into file and this results a larger file size and it's performance issue. Before deployment you should set the following tag

<compilation defaultLanguage="Vb" debug="false">

2. Set trace enabled="false"

How it affects performance: With help of tracing, we can track the application's and the sequences. Enabling tracing adds performance overhead and might expose private information, so it should be enabled only while an application is being actively analyzed. You can turn off tracing using

<Trace enabled="false" - - - - -/>

3. While developing using Visual Studio.NET

When you set Configurations Option as "debug" mode, it creates pdb file to store the debug information hence before deploying the application set it to the "Release" mode.

You can set using

Select Menu Build -> Configuration Manager -- > Set the configuration option of project to the "Release" mode.

4. Disable the viewstate:

With the help of automatic state management feature, the server control is re-populate their values without writing any code. And it affects the performance. The always set EnableViewState = false when not requires.

For control

<asp: datagrid EnableViewState="false" datasource="..." runat="server"/>

For Page

<%@ Page EnableViewState="false" %>

5. Use Caching to improve the performance of your application.

OutputCaching enables your page to be cached for specific duration and can be made invalid based on various parameters that can be specified. The Cache exists for the duration you specify and until that time, the requests do not go to the server and are served from the Cache.

Do not assign cached items a short expiration. Items that expire quickly cause unnecessary turnover in the cache and frequently cause more work for cleanup code and the garbage collector. In case you have static as well as dynamic sections of your page, try to use Partial Caching (Fragment Caching) by breaking up your page into user controls and specify Caching for only those Controls which are more-or-less static.

6. Use appropriate Authentication Mechanism.

Following are the Authentication Modes.

None
Windows
Forms
Passport

7. Validate all Input received from the Users.

Validate all Input received from the users at client side to avoid the server round trip.

8. Use Finally Method to kill resources.

Always use the finally block to kill resources like closing database connection, closing files etc.

9. Always use the String builder to concatenate string

The memory representation of string is an array of characters, So on re-assigning the new array of Char is formed & the start address is changed. Thus keeping the old string in memory for garbage collector to be disposed. Hence application is slow down. Always use the string builder for concatenating string.

10. Enable the web gardening for multiprocessors computers:

The ASP.NET process model helps enable scalability on multiprocessor machines by distributing the work to several processes, one for each CPU, each with processor affinity set to its CPU. The technique is called Web gardening, and can dramatically improve the performance of some applications

11. Set Enlist="false" in connection string:

True indicates that the SQL Server connection Pooler automatically enlists the connection in the creation thread's current transaction context. That's why set enlist = false in connection string.

12. Avoid recursive functions / nested loops

13. Always set option strict to "on"

14. Try to avoid Throwing Exceptions.