ASP.NET Session State Server vs. InProc Session

问题:

What is the overhead performance penalty for running Session State Server instead of InProc? Is it significant? I understand that you can restart w3wp with the state server and retain all session state - is that the only advantage over InProc?

回答1:

It depends on your deployment plans: on a single server, the penalty is small, but the benefit is equally limited: your session state survives process recycles (as mentioned) but that's about it. You'll have some cross process marshalling with StateServer mode, so expect some additional cpu load, nothing too impressive.

In a web farm/load balanced setup InProc won't work, unless you can configure sticky sessions/server affinity. Be mindful of the fact that the StateServer node itself can become a single point of failure, so be sure to compensate for that. Having said that, the latency of a StateServer is in general much less (= better) than when you use SQLServer mode.

Make sure that your code/site gracefully handles lost state, regardless of where you store the data.

回答2:

If you have a load balance setup (without the use of sticky sessions) you cannot use InProc since (based on your load balance setup of course) you might switch between nodes.

Recycles of the worker process (but that is of course the same as restarting w3wp) will also kill your session when it is InProc.