I am using ASP.NET, session state is stored outside the process in SQL Server. When a page request begins, all the contents of a user session extracted from the database, deserialized and sent to the ASP.NET process in one fell swoop, or individual objects transferred to the ASP.NET process only as necessary?
Basically, I have a page that stores some large objects in the session, and it's hard for me to determine when data can be deleted. If the data is extracted from the database only when it is used, then the problem does not arise; if all session state is placed in ASP.NET for every page request, I may have a performance issue.
source
share