《6 Ways to Kill Your Servers - Learning How to Scale the Hard Way》.pdf

/blog/2010/8/23/6-ways-to-kill-your-servers-learning-how-to-scale-the-hard-w.html 6 Ways to Kill Your Servers - Learning How to Scale the Hard Way Monday, August 23, 2010 at 7:58AM Todd Hoff in Strategy This is a guest post by Steffen Konerow, author of the High Performance Blog. Learning how to scale isn’t easy without any prior experience. Nowadays you have plenty of websites like to get some inspiration, but unfortunately there is no solution that fits all websites and needs. You still have to think on your own to find a concept that works for your requirements. So did I. A few years ago, my bosses came to me and said “We’ve got a new project for you. It’s the relaunch of a website that has already 1 million users a month. You have to build the website and make sure we’ll be able to grow afterwards”. I was already an experienced coder, but not in these dimensions, so I had to start learning how to scale – the hard way. The software behind the website was a PHP content management system, based on Smarty and MySQL. The first task was finding a proper hosting company who had the experience and would also manage the servers for us. After some research we found one, told them our requirements and ordered the suggested setup: ● LoadBalancer (+Fallback) ● 2 Webservers /developerworks 2012-11-11 整理 第 1／6页 /blog/2010/8/23/6-ways-to-kill-your-servers-learning-how-to-scale-the-hard-w.html ● Mysql Server (+Fallback) ● development machine They said, that’s gonna be all we need – and we believed it. What we got was: ● Loadbalancer (single core, 1GB RAM, Pound) ● 2 Webservers (Dual core, 4GB RAM, Apache) ● MySQL Server (Quad core, 8GB RAM) ● Dev (single core, 1GB RAM) The setup was very basic without any further optimization. To synchronize the files (php+media files) they installed DRBD in active- active configuration. Eventually the relaunch came – of course we were all excited. Very