This Sunday New York Times Magazine has an extensive article, Data Center Overload, about Data Centers and the Cloud as a new type of infrastructure. You know a topic has reached mainstream interest when it's in the Sunday Times.
While it's written for the lay person, I recommend you read it. The article talks a lot about the infrastructure, power, location, etc. The big stuff. The cool stuff. But this quote tells part of the story that touches on our topic of the Front Office.
Data centers, however, are loaded with inefficiencies, including loss of power as it is distributed through the system. It has historically taken nearly as much wattage to cool the servers as it does
to run them. Many servers are simply “comatose.” “Ten to 30 percent of
servers are just sitting there doing nothing,” Koomey says. “Somebody
in some department had a server doing this unique thing for a while and
then stopped using it.” Because of the complexity of the network
architecture — in which the role of any one server might not be clear
or may have simply been forgotten — turning off a server can create
more problems (e.g., service outages) than simply leaving it on.
Those servers are doing nothing because no one knows for what business purpose they were initially created. The number "10-30%" is huge and I believe it. And it has nothing to do with complexity of the network architecture and everything with request, lifecycle, and account management. This would allow us to know who the customer is, what's the intended lifecycle of those servers, etc etc.
This is why it's imperative for this large scale cloud computing to work that we architect the front office as much as we architect these noveau datacenters. No matter how big and scalable the cloud seems, without a front office even that capacity will not keep with demand.d
Maybe the tag line for the Front Office should be "Kill the Zombie Servers!"
Recent Comments