Slashdot Mirror
Amazon, MS, Google Clouds Flop In Stress Tests
Eponymous writes "A seven month study by academics at the University of New South Wales has found that the response times of cloud compute services of Amazon, Google and Microsoft can vary by a factor of twenty depending on the time of day services are accessed. One of the lead researchers behind the stress tests reports that Amazon's EC2, Google's AppLogic and Microsoft's Azure cloud services have limitations in terms of data processing windows, response times and a lack of monitoring and reporting tools."
Anna Liu, Associate Professor in services engineering at the UNSW School of Computer Science told iTnews she was excited by Cloud Computing as it could potentially enable organisations to "outsource a certain amount of their risks and costs and tap into new economies of scale."
Sounds more like she has a degree in buzzword engineering.
From her homepage at UNSW, it seems to be the creation and study of services but her focus seems to be on cloud computing with the "services" being concentrated on these subjects. While a lot of her about page seems to be buzzwords and journal writing, I really wish they would release their "interoperable service software" and would be interested in seeing their final report for more specific metrics. Her blog doesn't say much about it. I'd give her the benefit of the doubt, she says in the article, "We saw a lot of hype and confusion, and decided to lead a team of researchers and actually get our hands dirty with this stuff." She also said:
Using Google AppEngine, none of your data processing tasks can last any longer than thirty seconds, or it throws an exception back at you. This is very consistent with the Google business model - they want to enable simple web applications to thrive on the Internet. AppEngine is there to enable the rapid development of simple web applications that don't include intense compute at the back end. - Anna Liu
Which I found interesting. Again, kind of hard to judge the merits behind this research without even a brief description of what the services were ... a singular value decomposition service? A return huge data sets from a database table service? A prime factorization service? A file intensive I/O service? I'm also curious as to what hoops one has to jump through to get those interoperable across all three systems ... after all Microsoft is just .NET, right? Is this rewriting something 3 times or making shared objects or what?
My work here is dung.
Cloud computing has the benefit that when you need to expand your server park's capacity, you don't have to wait for several weeks for the hardware vendor to deliver the hardware. Instead you outsource that job to the cloud vendor. You can more quickly respond to both increase and decrease in traffic. During peak hours you can spawn a few more servers and at night you can shut down a few without having to worry about the physical hardware and their associated maintenance burden.
Essentially, it allows you to treat any net-connected computer as a dumb terminal with web services acting as your actual computer.
No kidding!!! What do you say at this point?