ASP.NET site is slow until it is redesigned

Question

I recently moved the site from IIS6 to IIS7 and am experiencing many performance issues.

Site performance is very poor until I redesign the application pool. What could it be a symptom?

I recycle all night, but that doesn't seem to be enough.

I don't rely so much on Session. Use caching quite a lot.

Answer 1

You can find very good guides for debugging the most common types of scripts for freezing, performance, memory, and crashing with .NET and ASP.NET here: .NET Debugging Demos - tuning and tuning instructions . These series are really worthy of attention, because they are full of information, but it takes quite a lot of time :-)

One of the common problems for server applications is allocating tons of "large" .NET objects that fall into the "Big heap of objects . " Check to see if you are actually doing a lot of byte[] or MemoryStream allocations exceeding 85Kb (objects with an adjacent size are larger than it will be in LOH, and this heap cannot be compacted). This typically happens if you create a large number of files (PDF, images, etc.), Copy, etc. This should be done using pure streaming without full-size allocations.

Answer 2

After releasing some new .NET components on my websites, I also experience application pool memory. I rewrite the memory manually (about once a day), but I'm going to complete a task that recycles the memory using treshold.

In any case, find instructions for cleaning, closing connections, destroying objects, etc.