ASP.NET session state and multiple worker processes
I need to understand something about ASP.NET session state, as it applies to IIS 7 and ASP.net 3.5.
I need to understand something about ASP.NET session state, as it applies to IIS 7 and ASP.net 3.5.
I have one website on my server, and my IIS Worker Process is using 4GB RAM consistently. What should I be checking?
What is the best practice for deciding how many worker processes to allow for an ASP.NET web application?
We have a fairly high volume ASP.Net site written in c# using MS commerce server, running in a 32-bit environment. I see the worker process up to 980 megabytes quite often. I would like to profile this process and determine where any gains could be made in code to reduce the memory foot print of this site. My question what tools have worked well for you doing this sort of thing on ASP.Net web applications?
I have a lot of Singleton implementation in asp.net application and want to move my application to IIS Web Garden environment for some performance reasons.