Last post Feb 07, 2009 09:41 PM by OWScott
Feb 05, 2009 02:46 AM|wdigby|LINK
I know this is one of those red-herring impossible to answer questions but let’s give it a go anyway. Apologies if it's in the wrong forum context also.
How do I select a server or servers to run my website? What variables do I put in such that I can get an idea of which dedicated option I should choose?
Presently I run two virtual private server accounts, one for IIS6 and one for SQL2005 and my site gets 200K users a month and around 3million page views. Growth is good, around 30% per month (but it is early days so I'm sure this will taper).
It is time to change hosting provider (because my current one charges too much for bandwidth) and so I'm thinking about getting 2 dedicated servers at theplanet.com
Cost is obviously a major consideration but are there best practices for selecting servers for what I want to do? E.g. Is Multi-core or Multi-processor a must for IIS or SQL Server? Is there some kind of memory per simultaneous connection ratio for IIS that
people go by? Am I better off getting 2 lesser machines and clustering IIS or is this overkill for a site my size?
I'd be grateful to hear of some experiences other people have.
Feb 05, 2009 11:20 AM|Enroth|LINK
You are right, it is better to ask at www.iis.net forums, use the same username/password as here.
My 2 cents: Multi-core or Multi-processor is not a must for IIS or SQL.
Feb 05, 2009 11:47 AM|HostingASPNet|LINK
What is the suggestion of your new ASP.NET hosting provider? If they are good in providing dedicated server hosting, they will talk with you and will offer a hardware depending on your needs. 30% is a good monthly growth, so it will be much better to get
more than you need.
Feb 07, 2009 09:41 PM|OWScott|LINK
There are a lot of things that define what hardware you need, mostly all within your control. The real answer is 'it depends'. Some sites can only handle a few simultaneous connections while others can handle thousands. IIS itself is rarely the bottleneck.
It can handle tens of thousands of simultaneous connections per second on a good server before it starts complaining. The issues are with your site itself, for example ASP.NET and the database.
I would suggest taking your application and simulating a lot of traffic and seeing how it handles. Then try to compare your test environment to the production to estimate what you need with your host. There are lots of good load testing tools out there.
WAST are a couple freely available options.
Regarding 1 or 2 servers: 2 smaller web servers with 1/2 the resources will perform about the same as a single web server. There aren't any fancy considerations in that regard. Having SQL Server on its own server is helpful unless you have a relatively
small site. That allows you to tune and grow the two servers independently. But, if you want to make sure that your site can survive hardware failures, then it's worth considering it for availability reasons, rather than scalability reasons.
(oh, and if you want a host that may not be the cheapest, but that can scale with you to any size, consider
www.orcsweb.com. We can work with you for your sizing and growth needs, up-front and as you grow)