Clever Geek Handbook

Estimating the number of ASP.Net servers

Suppose our average page weights are P KBytes and we have N visits per unit of time (let's say, per hour). How can we estimate the number of servers needed to support this load with reasonable response times?

0


source to share


1 answer


There are so many server performance factors (CPU, RAM, I / O, cache, local or external database, networks, etc.) that you cannot even count the number of servers required for a given project.

I find that anyone trying to figure this out is on the wrong track because they often have an unrealistic idea that the site they are going to make is going to be insanely popular.



My advice is to just build an application and use 1 server, let's assume you might need a server farm, so build your software according to (which in .NET pretty much means you don't do anything else). Buy more servers when you have a real need, buying / renting servers pending will always be a waste of money, you are not Amazon and Google, you cannot predict future expansion until you see the current numbers.

I think you will find 1 good server surprisingly fast and can handle a lot of users. Keep in mind that StackOverflow (last I saw) only works on 2 servers; web server and database server ... that's it.

+4


source






More articles:


All Articles