out of process session state - how much slower?

[Guest]

Hi peeps

I'm having some problems with my Session State sticking (it keeps resetting
itself) - I haven't looked into it yet, but I was wondering about using SQL
Server as an out of process state manager?

I've heard it's slower - and I was just wondering... how much slower? (this
is for an Intranet app)

Cheers



Dan

 

[Marina]

We actually roll our own session state, but we have an option to keep it in
sql server. I have to say, I have not noticed a performance difference, nor
have heard of anyone else who has.

To see how much slower it would be, I would say, try it out. Do some
performance benchmarks with the 2 different types of session state.

 

[Steven Berkovitz]

If my memory serves me correctly (and someone please correct me if I'm
wrong) but:

StateServer ~ 10 % loss
SqlServer ~ 20% loss

 

[Juan T. Llibre]

The key is : 10-20% of *what* ?

If it's 10-20% of a few milliseconds,
does it impact performance all that much ?

A key element will be network lag.

If there's packet latency in your network, and your State Server
or your SQL Server are downline from your web server, that will
have considerably more impact on performance than the almost
negligible performance impact of having State Server or SQL server
maintain state, instead of maintaining state with Inproc.

Also, if you absolutely need to maintain state out-of-process,
then whatever performance cut is taken will be worth it.

 

[JIMCO Software]

Hi peeps

I'm having some problems with my Session State sticking (it keeps
resetting itself) - I haven't looked into it yet, but I was wondering
about using SQL Server as an out of process state manager?

I've heard it's slower - and I was just wondering... how much slower?
(this is for an Intranet app)

I would always refer to Pat Ng's Session FAQ.

http://forums.asp.net/7504/ShowPost.aspx