Performance Optimization
Hi,
We hosted WSS 2.0 in our org. as a server farm. All our servers are high end servers with Intel Xeon 3GHz processors, 4GB ram, 200GB Harddsik etc. It takes approx 50-60 secs for the home page to load in http:// and more than 5 mins in https://
But, Our web server is running in a seperate n/w (ie., 10.101.xxx.xxx) with a link speed of 100Mbps and our DB server is placed in a seperate n/w (ie., 10.100.yyy.yyy) with a link speed of 1Gbps. Will this affect the n/w performance?
How can increase the speed of my server or what should i do to improve the performance?
Thank you.
hi,
I had nearly the same problem.I assigned more worker processes to the IIS application pool, this solved the problem.
IIS Manager > Application Pool properties > Performance
you can assign 1 workerprocess per 600MB RAM
regards
I am also facing same type of performance problem.
i went to application pool->properties->performance.
In that in the "maximum number of worker processes", it is set to 1.
My ram is 1 gb.So should i increase the ram to 3 gb and then assign 4 or 5 worker processes.can somebody please give me why it increases the performance if i do like that.i presume that central administration site, works in the same app domain and hence under same worker process. then how it will make a difference.
Also i want to do capacity planning so that i can add servers according to number of users, hits etc,
Can somebody please help me in this
Cheers
Leo,
IIS app pools are often overlooked and do need carefull planning.
As a rule of thumb if you have 1 WSS application (ignore central admin as the load on this is limited) and you have 4GB ram you should set it too 3 worker processes with 600MB each. (it used to be 800MB when the option to use the /3GB switch was available see blog post on this).
The use of multiple worker processes allows each web front end server to have a web garden where it balances the load between processes. This allows each process to recycle if it needs to (it will use up its memory at some time) without the server going down, it also allows the server to process addtional requests when there is a long running tranaction/process as the server will not queue the requests.
Regarding capacity planning I recommend you look at Joel Olesons excellent post on this.
Andrew
These performance numbers are so far from acceptable that I would be amazed if anyone used it.
I would expect a performance of < 5 seconds for any homepage to load. You need to look at the following to start with but your setup does not sound healthy
1) do you have any poorly developed custom code on the home page
2) Do some performance measures on the servers, do you have lots of transactions queuing
3) Is the network causing the issue (firewalls, routing errors)
4) Is SQL underload (processor, memory)
Andrew
