![]() You can read the details at: 2.8 million page views per day: 70 million per month: one server!Īfter consulting with the client, we recommended to go a step further and use the additional budget, and implement a near fault tolerant setup. The setup is mostly like what we did for another much higher traffic site. Instead of using Varnish, we used only memcached. We then did a full server installation, configuration, tuning and optimization tuning the entire LAMP stack from scratch, on our recommended Ubuntu 8.04 LTS Server Edition. The server is quad core Xeons E5620 at 2.4GHz, 8GB of RAM, 4 disks (each 2 forming a mirror). The SolutionĪfter doing a full Drupal site performance assessment, recommended and implemented a new setup consisting of a single medium sized dedicated server for $536 per month. The site was sluggish most of the time.įinally, the setup was not able to handle traffic spikes adequately. ![]() Third, the cost is too high compared to a single well configured server, at almost half the cost.įourth, Amazon's ELB Load balancer forces the "Fifth, the performance was not up to par. However, if there is a database server or NFS server crash, the entire setup would stop serving pages. The only part that is redundant is the web server, with two of them present. Setup Drawbacksįirst, there is complexity: there are many components here, and each required patching with security updates, monitoring of disk space and performance, and other administration tasks. Storage and bandwidth brought the total to $990 per month. The cost was high compared to the features: EC2 computing cost alone for the instances was around $920 per month.Īdditionally, there were 331 million I/O requests costing $36 per month. The setup relied on Amazon's Elastic Load Balancer (ELB) front ending the site.īehind the load balancer, there were a total of 4 instances, varying in type.įirst, there were two web servers, each one of them m1.large.Īnother m1.small instance acted as the NFS server for both web servers.įinally another m1.large instance housed the MySQL database. The site was originally hosted at another big name hosting company, but unfortunately they went down several times due to data center power issues.Īfter moving to Amazon AWS, with the setup below, the site was a bit sluggish, and when the traffic spikes described above happened, the setup could not cope with the increased traffic load. ![]() The client is a specialized news site, and gets linked to often from other high traffic sites such as Yahoo's front page, and the Drudge Report. ![]() Here is a case study of a client that was on Amazon until recently, and we moved them to a more custom setup, with great results. We certainly like Amazon AWS for development and testing work, and for specific use cases such as seasonal sites.įor most high traffic sites though, Amazon AWS can be overly expensive, and not performant enough.īefore you decide to use Amazon, spend some time studying the various Amazon instance types, and the pricing that will be incurred. Among those are: instant provisioning of virtual servers, billing for used resources only, ability to provision more instances on demand, a wide variety of instance types, and much more. Sadly, this is normally done without really doing a proper evaluation into whether the cost is reasonable, or the technology is suitable for their specific needs.Īmazon AWS provides some unique and compelling features. With the "Cloud" being in vogue currently, we see a lot of clients asking for cloud solutions, mostly Amazon AWS.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |