We have a ASP .Net 4.0 website that currently uses InProc session. But would like to move it to a web garden/farm and would like to move the session to out of proc. What is the current recommended way for session storage for large websites?
If the ideal case is more time consuming to setup, I would like to hear some intermediate step that we could use to set this up quickly and implement the ideal case down the road. I've heard/read memcached, ASP .Net Session State server, etc. What's easy
to set up and what is the ideal way for scalability/performance.
We are also in development and deployement of a large scale web application developed in asp.net 4.0.
In my recent study and after reading many articles, the inProc session is much faster than the outProc sessions. As the inProc session is used the server memory, we need to do compromise in that part. If we use outProc session management either using SQL
Server/State Server there may be a performance down upto 15% as compared to inProc session.
We are now using SQLServer for session management, as our application have multiple application as subdomain, and we need to use the same session for all the application.
Thanks & Regards
---------------------------------------------
Jinto George
Founder - www.rupeehunt.com
It's how you use the cache. The assumption is that the cache will be gone perodically so you only put data in the cache that you can reload from the original data source.
tpa
Member
40 Points
10 Posts
Session State - Recommended/Best Practices for storing ASP .Net sessions
Jan 20, 2013 03:03 AM|LINK
Hi,
We have a ASP .Net 4.0 website that currently uses InProc session. But would like to move it to a web garden/farm and would like to move the session to out of proc. What is the current recommended way for session storage for large websites?
If the ideal case is more time consuming to setup, I would like to hear some intermediate step that we could use to set this up quickly and implement the ideal case down the road. I've heard/read memcached, ASP .Net Session State server, etc. What's easy to set up and what is the ideal way for scalability/performance.
JintoGeorge
Member
2 Points
1 Post
Re: Session State - Recommended/Best Practices for storing ASP .Net sessions
Jan 20, 2013 05:34 AM|LINK
Hi,
We are also in development and deployement of a large scale web application developed in asp.net 4.0.
In my recent study and after reading many articles, the inProc session is much faster than the outProc sessions. As the inProc session is used the server memory, we need to do compromise in that part. If we use outProc session management either using SQL Server/State Server there may be a performance down upto 15% as compared to inProc session.
We are now using SQLServer for session management, as our application have multiple application as subdomain, and we need to use the same session for all the application.
Thanks & Regards
---------------------------------------------
Jinto George
Founder - www.rupeehunt.com
BrockAllen
All-Star
27516 Points
4898 Posts
MVP
Re: Session State - Recommended/Best Practices for storing ASP .Net sessions
Jan 20, 2013 04:47 PM|LINK
Large websites tend not to use session due to the impact on scale and correctness. Here's my take on it.
DevelopMentor | http://www.develop.com
thinktecture | http://www.thinktecture.com/
tpa
Member
40 Points
10 Posts
Re: Session State - Recommended/Best Practices for storing ASP .Net sessions
Jan 21, 2013 02:04 PM|LINK
Thanks guys for the info.
BrockAllen - Isn't Cache part of the application object? How does it work/scale if you have a web garden/farm?
BrockAllen
All-Star
27516 Points
4898 Posts
MVP
Re: Session State - Recommended/Best Practices for storing ASP .Net sessions
Jan 22, 2013 02:41 AM|LINK
It's how you use the cache. The assumption is that the cache will be gone perodically so you only put data in the cache that you can reload from the original data source.
DevelopMentor | http://www.develop.com
thinktecture | http://www.thinktecture.com/