Re: Using ASP.NET StateServer on another machine. So what?
From: Joe Fallon (jfallon1_at_nospamtwcny.rr.com)
Date: 10/17/04
- Next message: Joe Fallon: "Re: how to send two parameters in HyperLinkColumn?"
- Previous message: niv: "tabindex on webform"
- In reply to: GeekBoy: "Re: Using ASP.NET StateServer on another machine. So what?"
- Next in thread: GeekBoy: "Re: Using ASP.NET StateServer on another machine. So what?"
- Reply: GeekBoy: "Re: Using ASP.NET StateServer on another machine. So what?"
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 17 Oct 2004 15:23:49 -0400
You will never get a perfromance increase when moving from InProc to State
Server.
You will always get a decrease.
What you get in trade is increase in stability.
-- Joe Fallon "GeekBoy" <geekboy0001@yahoo.com> wrote in message news:b0f9709c.0410160529.41ca3795@posting.google.com... > For those two reasons, I agree completely. However, for one webserver > how much of a difference could it possibly make? I think, if you're > careful with your session variables (I only have three simple types) > then it might even be worse performance including the latency across > your network... so, why bother storing it on another machine? Has > anyone noticed any performance increase by off-loading the state > server to another machine? > > > "Joe Fallon" <jfallon1@nospamtwcny.rr.com> wrote in message > news:<uCMPTAzsEHA.2316@TK2MSFTNGP12.phx.gbl>... >> It is useful for a few reasons. >> >> 1. When you use InProc the session variables can be lost when the process >> gets recycled. >> This is the main reason for using StateServer. (Even if it is on the same >> local box. You do not need 2nd box just for State Server.) >> >> 2. Web Farms can have multiuple boxes all pointed to the same State >> Server. >> This lets you avoid "sticky sessions". Then you can truly load balance >> the >> servers in the farm. >> >> -- >> Joe Fallon >> >> >> >> "GeekBoy" <geekboy0001@yahoo.com> wrote in message >> news:b0f9709c.0410151629.554da1a4@posting.google.com... >> >I understand the benefit of pushing the StateServer process onto >> > another computer to "balance" the load and take some cpu and memory >> > usage off the web server, but how much could it possibly help? >> > Especially when you're talking about marshalling the data back and >> > forth across your network (although on the same segment)? >> > Here's my scenario: Each login stores exactly 3 session variables; one >> > integer and two strings. That's it. Never, ever, is anything else >> > ever stored in a session. We have a couple hundred users. So what? >> > I mean, how much could moving the StateServer process to another >> > computer REALLY help? I tried it but don't notice anything. This >> > week, I'll be monitoring memory and cpu usage but my initial trials >> > show nearly no difference at all... might as well use that other PC >> > for something more useful. >> > Thoughts?
- Next message: Joe Fallon: "Re: how to send two parameters in HyperLinkColumn?"
- Previous message: niv: "tabindex on webform"
- In reply to: GeekBoy: "Re: Using ASP.NET StateServer on another machine. So what?"
- Next in thread: GeekBoy: "Re: Using ASP.NET StateServer on another machine. So what?"
- Reply: GeekBoy: "Re: Using ASP.NET StateServer on another machine. So what?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|