Geek Answers Handbook

Session State Reservation

We currently have an ASP.NET web application running on a single server. This server is going to get into the danger zone regarding CPU usage, and we want to deploy a second server.

What would be the best way to handle session state?

We are currently launching InProc. But this is not an option with 2+ servers, since we sometimes want to exclude one server from WLB in order to perform maintenance work. Despite the fact that we use sticky load balancing, we will have to wait for all users to exit before we can exclude the server from WLB rotation.

So, I looked at this MSDN page: http://msdn.microsoft.com/en-us/library/ms178586(VS.80).aspx

I guess my main question is : if we use State Server mode. Can we provide rendudancy by deploying a public server on two servers? To avoid a single point of failure.

+4
source share
5 answers

If you need one of the standard options, I would use SQL Server in a failover cluster. By the way, do you consider memcacheddb?

+1
source

Use a Scale Out State server (faster) or SQL State (slower easier). But be careful if you do not save any serializable objects in session state because you will get exceptions after the migration.

0
source

Sql State server would be the best option: this link can help Sql State Server . I do not believe that you can run the state server on multiple computers.

0
source

you may need to study the speed of the project ( http://msdn.microsoft.com/en-us/data/cc655792.aspx ). Now it has limited support because it is on CTP3, but at the end of this year it will be RTM. I highly recommend you watch the MIX09 session about it here.

0
source

I would suggest looking at the p2p Session State Server - the link is here: http://www.codeproject.com/KB/aspnet/p2pstateserver.aspx

Worked for me. The only drawback is that if you have a large data set, then it is forever replicated between peers.

0
source

More articles:


All Articles