I'm troubleshooting some memory issues we're running into with a heavily used ASP.NET site hosted on IIS6. Intermittently we have to manually recycle our application pool (process) to resolve issues in browsing the application and its been increasing over the last few months. I analyzed our web logs and found some interesting info:
- At the times where performance suffers most, I see that also correlates with the number of concurrent user sessions.
- It seems that user activity and # of hit does not matter as much as the number of sessions because there are days with HEAVY user activity (hit-wise), but no recycle was needed. The number of sessions were low during those times. Conversely, lighter usage but more user sessions ultimately meant a recycle.
Here is my question: Considering the info above, is there some overall memory limit for session data that we're hitting??
I'm thinking that the more user sessions created, the more memory is allocated per session and at some point we're exhausting the resources, which gets resolved with each recycle.
Does that theory make sense? Any help is appreciated. Thanks!