Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
What various methods and technologies have you used to successfully address scalability and performance concerns of a website? I am an ASP.NET web developer exploring .NET remoting with WCF with SQL clustering and am curious as to what other approaches exist (such as the ‘cloud’). In which cases would you apply various approaches (for example method a for roughly x many ‘active’ users).
An example of what I mean, a myspace case study: http://highscalability.com/myspace-architecture
This is a very broad question making it difficult to answer, but I’ll try and provide a few general suggestions.
1 – Unless you are doing some things seriously wrong then you’ll likely not need to worry about perf or scale until you hit a significant amount of traffic (over 1 million page views a month).
2 – Your biggest performance problems initially are likely to be the page load times from other countries. Try the Gomez Instance Site Test to see the page load times from around the world, and use YSlow as a guide for optimizing.
3 – When you do start hitting performance problems it will first most likely be due to the database work. Use the SQL Server Profiler to examine your SQL traffic looking for long running queries to try optimizing, and also use
dm_db_missing_index_detailsto look for indexes you should add.4 – If your web servers start becoming the performance bottleneck, use a profiler to (such as the ANTS Profiler) to look for ways to optimize your web pages code.
5 – If your web servers are well optimized and still running too hot, look for more caching opportunities, but you’re probably going to need to simply add more web servers.
6 – If your database is well optimized and still running too hot, then look at adding a distributed caching system. This probably won’t happen until you’re over 10 million page views a month.
7 – If your database is starting to get overwhelmed even with distributed caching, then look at a sharding architecture. This probably won’t happen until you’re over 100 million page views a month.