Dos anyone can talk about the configuration of web farm on windows platform.Not the load balancing part but the other stuffes.Thanks
k*i
2 楼
Just try a littlbe bit.What you need to do is: 1.Make sure the application path in IIS metadata is the same for every server(use metaedit.exe to check) 2.use the same descryption and validation key on every server(in machine.config) 3.use StateServer or SqlServer to maintain the session information 4.Load Balancing.
【在 k****i 的大作中提到】 : Dos anyone can talk about the configuration of web farm on windows : platform.Not the load balancing part but the other stuffes.Thanks
【在 k****i 的大作中提到】 : Just try a littlbe bit.What you need to do is: : 1.Make sure the application path in IIS metadata is the same for every : server(use metaedit.exe to check) : 2.use the same descryption and validation key on every server(in : machine.config) : 3.use StateServer or SqlServer to maintain the session information : 4.Load Balancing.
k*i
4 楼
This could be handle by some tools bah. It's said that the penalty would be greater than 25% when using sql server and 15% for state server
and Usually there's no performance panelty in total. But I suggest to use StateServer.
【在 k****i 的大作中提到】 : : This could be handle by some tools bah. : It's said that the penalty would be greater than 25% when using sql server and : 15% for state server
d*e
6 楼
what kind of tool can do that? on each server or on somewhere else? and it seems a lot. but if we can increase the number of servers in the farm by 25% then i guess we can offset it. then, the database will ve very busy. and
d*e
7 楼
where will you put the state server? a dedicated machine?
【在 C****n 的大作中提到】 : : and : Usually there's no performance panelty in total. : But I suggest to use StateServer.
C*n
8 楼
Doesn't matter, sometimes I use 127.0.0.1 :-) It's perfectly OK to use one of the webserver as StateServer. All depends on whether you website is really that busy.
k*i
9 楼
So do you have the idea how to dispatch the request?Response.Redirect just doesn't work for cookie session.
【在 C****n 的大作中提到】 : Doesn't matter, sometimes I use 127.0.0.1 :-) : It's perfectly OK to use one of the webserver as StateServer. : All depends on whether you website is really that busy.
e*g
10 楼
why not use a load balancer which always dispatch same session to same server, based on cookie. not even hard to write one in software. every request involves a remote call, that's too bad. and it's a single point of failure.
k*i
11 楼
So if the server is doing some load intensive job,you still pass the request to that server?That's not a good choice 【 在 embug (小甜甜) 的大作中提到: 】
d*e
12 楼
what if the server which starts the session died? bad user experience. it can be solved by having persistant state. I think the multiple servers in the web farm not only can balance the load, but also act as sort of redundancy to each other.
【在 e***g 的大作中提到】 : why not use a load balancer which always dispatch same session to same : server, based on cookie. not even hard to write one in software. : every request involves a remote call, that's too bad. and it's a : single point of failure.
e*g
13 楼
sure you can do session replication and recovery on background. crash concern doesn't have to sacrifice performance for 99.9% case. but i guess you can only use whatever MS provides.
【在 d******e 的大作中提到】 : what if the server which starts the session died? bad user experience. it can : be solved by having persistant state. : I think the multiple servers in the web farm not only can balance the load, : but also act as sort of redundancy to each other.