Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Okay, I know you shouldn’t keep too much in session, and it’s more of an architectural issue than anything else (move the session state to another server, db, load balance web server), but is there a way to tell .net to start scavenging for ram if there is too much being stored in session?
There is nothing built in that monitors the size of sessions, so you may have to build one yourself.
Consider using the
Cacheclass – it has size controls that will evict older entries for newer ones and you can use a session ID as part of the cache key.