ASP.NET "Re-establish Session" Performance Hit -
ASP.NET "Re-establish Session" Performance Hit -
after user has established session asp.net, each subsequent http request how much of stateserver session objects immediately , automatically fetched , deserialized? example:
are all session objects fetched moment request received , session re-established, or... after session re-established session objects fetched , deserialized individually each request httpcontext.session["..."] made?the reply has huge impact on how can utilize session. example, if have pre-fetched important amount of user info session, , stateserver session deserialized upon each http request, experience noticeable performance hit. if pre-fetched user info deserialized when request specific session keys, me there no worry.
update after marking reply question, discovered asp.net appfabric server 1.1 has alternative have session restored on-demand rather all-at-once. controlled useblobmode in web.config.
session
loads of user session
info when page first loaded. persists users session info store after page done processing.
you can improve understanding via msdn on custom state store implementations.
this major reason you're supposed utilize session possible because expensive deal (both in transporting , info store , holding of info in memory lifetime of page request).
asp.net performance session
Comments
Post a Comment