[asp.net] session state management / performance

Posted By: miies | May 18th, 2004 @ 5:14 AM
page 1 of 1
Comments: 3 | Views: 7553
#May 18th, 2004 @ 5:14 AM
miies
miies
I'm curious to your experiences with performance gains/losses with the different types of session state management (InProc, StateServer, SQLServer).
 
InProc is pretty much unusable in our projects due to building/deploying issues, so I have the choice: aspnet_state.exe or SQL Server? Probably both have their pros and cons, but which one do you think is 'best'?

Links to webpages/articles are of course very welcome, too.

Thanks,
Michel
#May 18th, 2004 @ 6:58 AM
LazyCoder
LazyCoder
I'm still trying to figure out why my app occasionally loses the Session vars altogether. It's like the process restarts, but it doesn't show in the event log as having restarted. It's more like the session state just resets and I lose all my values. I'm sure it will take a lot of man hours to find.
#May 18th, 2004 @ 8:48 AM
GooberDLX
GooberDLX

in reply to LazyCoder, everytime you change the global.asax, web.config, or dll files, it will cause you app to reset.. ALSO, you can go to the properties of the Application Bag for which your asp.net app is attached to, and look at the worker thread config. something may have been changed?

in reply to miies
aspnet_state.exe or SQL Server...

with SQL Server, your session can persist permanently and is most secure, yet it requires an SQL transaction during session state management, something that can become quite costly..

Im not too sure about the session server (out-of-proc).. but I usually only hear people using inproc or sql

THIS forum at ASP.net Forums is GREAT .. they answer quite quickly and there is TONS of information to go through.
http://www.asp.net/Forums/ShowForum.aspx?tabindex=1&ForumID=22

Jake

#May 18th, 2004 @ 9:59 AM
miies
miies
Thanks. I've found some hard figures (more or less) in this, very informative, article by Dino Esposito:

http://www.vsj.co.uk/articles/display.asp?id=286

StateServer: approx. 15% overhead
SQL Server: approx. 25% overhead
page 1 of 1
Comments: 3 | Views: 7553