scaling - when to start performance tuning a website -


I have an asp.net mvc website and the volume of traffic is increasing. I have a site pointing to a backend SQL Server 2008 database.

At what point, I need to understand what the system is obstructing and if I need to load the balance machine or be reviewed by the way I am managing the database connection.

Are there specific tools and thresholds, which are not currently scalable to the current model or a breaking point (except for a slow site commentary) P>

There are some very easy things you can do to increase performance with so little work, it's easy to do this, see what you have to do yet;)

First and foremost all static images and other media That is put on a different server eliminates completely the questions on Boksen running dynamic parts of the Web server.

The next line ensures that you are using the hard drive spindle as much as possible, of course you want your database on a different machine, a separate hard drive alone, but you also want to Your web server logs on a different hard drive. It jumps around many heads of hard drives.

As far as "You know that when you need to perform a performance", I will give a different answer than George Stoker: the cost associated with your performance, the cost to consider Moves forward. I call it this way because your customer may be a little disappointed if your website is a bit slow, but if it does not prevent anyone from using it, or it does not recommend to others, then it is possible Do not seem. People adopt with all-optimal performance at all times.


Comments

Popular posts from this blog

asp.net - Javascript/DOM Why is does my form not support submit()? -

sockets - Delphi: TTcpServer, connection reset when reading -

javascript - Classic ASP "ExecuteGlobal" statement acting differently on two servers -