How to improve the performance of an ASP.NET application? Which are are the fields I should take care? The application includes DB connections and Image Parsing etc.
Answers:
Thank you for visiting the Q&A section on Magenaut. Please note that all the answers may not help you solve the issue immediately. So please treat them as advisements. If you found the post helpful (or not), leave a comment & I’ll get back to you as soon as possible.
Method 1
10 Tips for Writing High-Performance Web Applications
20 Tips to Improve ASP.net Application Performance
Bye
Method 2
I wrote a book about this that was just released, called Ultra-Fast ASP.NET: Build Ultra-Fast and Ultra-Scalable web sites using ASP.NET and SQL Server.
The book is about 500 pages long, so there’s a fair amount you can do, at all tiers: client (HTML/JavaScript structure), IIS, ASP.NET, SQL Server, infrastructure, etc.
Method 3
try avoiding unnecessary postbacks to pages, there are a lot of features you can implement by using things like jQuery or ExtJs framework. Learn how to do AJAX calls and pass info between your app and the server via JSON result sets.
Also, install apps like FireBug and YSlow and use these to analyze your application and follow their recommendations on how to speed up your app. Good luck!
Method 4
- HTTP Compression
- Disable Possible ViewState
- Changes in the Web.Config File :
Use page caching,
Remove unnecessary httpModules,
Turn off trace,
Disabled automatic save for profiles,
Set debug=false. - Implement Cache Dependency
- Optimize Stylesheets
- Optimize JavaScript
- JS and CSS File Position
- server.transfer() Instead of response.redirect()
- Client-side Script for Validation
Method 5
The book Improving .NET Application Performance and Scalability has a chapter on Improving ASP.NET Performance, that might be worth reading. The full book is online at MSDN, and is also available as a PDF download.
Method 6
Here’s an excerpt from the book Jeff, Phil, and K. Scott Allen wrote:
8 ASP.NET Performance Tips. It’s a few years old, but most of it’s pretty timeless.
My checklist:
- Find out what’s slow by testing
- Cache what you can (application cache, output cache, etc.)
- Reduce page size (eliminate viewstate, compress images, use CSS instead of inline styles, etc.)
- Find out which external dependencies are slowing you down (worst queries, webservices, etc.).
- Offload processing to the client (jQuery for filtering vs. round trips to the server to server to re-query)
Method 7
Use the .NET CLR profiler to determine where optimization will be useful.
http://msdn.microsoft.com/en-us/magazine/cc301839.aspx
All methods was sourced from stackoverflow.com or stackexchange.com, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0