Delayed ASP.NET Session Counter (perfmon.exe)

Question

I am currently downloading an ASP.NET application. I charge 500 users in the application, and while it works, I check the Session Actives and Session Timed Out counters in the perfmon.exe console on the web server.

In my web.config, the session timeout is 3 minutes (for testing purposes).

So, as the test passes, the "Session Actives" counter is located in approximately 900 active sessions, which, I believe, is normal due to 500 active users and about 400 others whose sessions are not yet timed.

But when I look at the Session Timeout counter, it increases every time. It just gradually drops when the load test ends.

What is this counter? As far as I understand, these are obsolete sessions that have not yet been cleared (by the garbage collector?) And are still using memory.

Since our application uses a huge amount of memory, I am trying to find where exactly this memory is located.

Answer 1

The counter seems to indicate what is happening. those. as active sessions, the counter for active goes to the desired number .. and at some point they begin to die, and they cause an increase in session time (i.e., sessions that are generally terminated by ASP.NET). I'm not sure what you expect to see. I recommend reading chapters 15 , 16, and 17 Improving the performance and scalability of .NET applications . In this regard, they are quite enlightening.