I think that 15% figure comes from Dino Esposito's ASP.NET book. My own
consistent basis. There are certainly overriding factors such connectivity
etc. Anyway, 15% is manageable for most real world applications that concern
"Juan T. Llibre" <nomailreplies@nowhere.com> wrote in message
news:%230%23zrZ8DFHA.4032@TK2MSFTNGP10.phx.gbl...
> True,
>
> but I'll take a 15% performance hit any day,
> against the possibility that *100%* of my
> clients lose their session variables.
>
> Site performance should be measured before making a
> move from InProc to State Server Sessionstate management.
>
> If more hardware is needed, to make up for the 15%
> performance loss, it sure would be a good investment.
>
> But maybe the 15% perf loss wouldn't matter,
> if there's enough of a perf "cushion" which could
> serve to compensate that 15% perf loss.
>
>
>
>
> Juan T. Llibre
> ASP.NET MVP
>
http://asp.net.do/foros/ > Foros de ASP.NET en Español
> =====================
>
> "Ollie" <why do they need this!!!!> wrote in message
> news:ewokGM7DFHA.1264@TK2MSFTNGP12.phx.gbl...
>> moving from in-proc to out-of-proc session state is definitely going to
>> give worse performance, a good article can be found at
>>
>>
http://www.eggheadcafe.com/articles/20021016.asp >> HTH
>> Ollie Riches
>
>> "Steven Spits" <someone@company.com> wrote in message
>> news:OtQ%23VJ7DFHA.1936@TK2MSFTNGP14.phx.gbl...
>>> Hi,
>>>
>>> We're thinking of moving session from inproc to a state server. My
>>> question is: should we expect a difference in performance? Is it
>>> noticeable?
>>>
>>> Steven
>>>
>>> - - -
>>>
>>>
>>
>>
>
>