MisterX said:I'm interested in this as well. It would be nice to hear more details about some of your experiences and solutions.
theNOTO said:Well the first thing you have to do is determine the bottleneck. This could be the database using 90% of the CPU cycles, it could be bandwidth, it could be general CPU overload from requests.
Then, based on the bottleneck, you balance things out by distributing the load over several servers, putting the DB on its own server, etc.
Every scenario is unique depending on CMS, DB choice, DB size, available bandwidth, etc.
peach said:How do you go about looking for bottlenecks?
Payton said:unfortunately this might be tough to find on shared hosting, you would probably have to contact your hosting company when you have slowdowns
if you have root access you can run top and see what's running