I’ll blog about effective production memory profiling techniques (hint: without using a memory profiler) in a future post.
Watching for and fixing these 3 low-hanging issues could make a big difference in the performance of your ASP. There are many other common wins for increasing IIS/ASP.
Especially when you consider the overhead of per-request query compilation on application CPU usage, and not just the execution speed of the query itself. The CLR Garbage Collector (GC) automatically cleans up unused objects allocated by your application in the background.
We finally come to the last, and possibly the most important, cause of wasted CPU cycles/bad performance for ASP. This process can be very efficient for well-tuned applications, but for many applications it can take up anywhere from 10% to 50% or more percent of the CPU time.
As it turns out, most applications end up breaking this advice here and there.
This often happens when dealing with potentially error prone code, which is sometimes wrapped in a try/catch instead of figuring out why its throwing an exception in the first place.
Having said that, the most direct way to improve performance is to proactively monitor it and periodically load test/profile it to address the actual bottlenecks in your code.Its a free 5-7 email course that teaches the production troubleshooting techniques we’ve been using for years.) It can’t possibly be that easy, can it?If you’ve ever done a performance investigation in production, you know the drill.In the last 5 years, we’ve helped hundreds of companies address performance problems in their IIS & ASP. Many of them had the same common problems when it came to high CPU usage.The good news is, several of these problems are very easy to fix.