When it comes to video production, cloud solutions may contribute significantly to energy consumption.
The cloud is widely proposed as the latest solution for at least three key media and business applications, including: Storage as a service (STaaS), Software as a service (SaaS) and Processing as a service.
In production and broadcast environments, all three applications are sometimes seen as viable answers to the needs of a fast-paced media production center. Even so, it’s the storage as a service product that is seeing the early application in the video production arena.
Storage as a service (STaaS)
Some common commercial products of STaaS include Instagram, DropBox and Carbonite. Professional STaaS services are available from Amazon (Amazon S3), Microsoft (SkyDrive) and EMC (Atmos), among others. All of these products do pretty much the same thing — you upload your data, and the company stores it. The services rely on users with a standard desktop, laptop or even a thin client to access to the data. If your application needs to store Exabytes of data these services can be helpful and inexpensive.
With storage costs dropping, one might ask why not build your own storage application and house the data on-site. The other side of that same coin is, “Why bother? Let someone else handle the data.” There are several reasons, both pro and con, to storing data locally. Among reasons to store data locally, doing so offers security, fast transfer and full control. On the other hand, using an off-site provider potentially lowers operational costs, means no hardware upgrades or system management and allows for access from anywhere. A long debate can be had on each of the above points, but we will let them serve as their own basis for discussion over this series of articles.
More power efficient?
There is, however, an oft-touted benefit of using the cloud for data storage, and that is power savings. Broadcasters are only now becoming aware of the importance of controlling power costs. Moving forward, technical managers can expect federal, state and local government bureaucrats to increasingly drive companies to use less electricity. One proposed way to reduce electrical costs is to move large-scale data storage off-site to a server farm. A huge server farm may be more efficient, have newer servers consuming less power and operate with lower costs than can a local production or broadcast house — right? Cloud storage providers may tell you so, but the real answer requires a bit of investigation. Let’s look at a real-world example.
In July 2011, the General Services Administration (GSA) announced it was the first federal agency to completely migrate its e-mail system to the cloud. The company overseeing the project, Unisys, claims to have completed the move of 17,000 employees to Google Apps for Government. The entire system now runs on Google’s cloudbased storage and email system. The conversion process required just more than a year. According to Google, that project saved the GSA 93 percent on GSA’s annual server energy costs. Google claims GSA’s annual electrical operational costs dropped from $307,400 to only $22,000. (See Table 1.)
Table 1. This table shows a before-and-after effect on energy consumption and costs, as reported by Google, for the GSA after the agency migrated its e-mail system to the cloud and Google Apps for Government.
With regards to the GSA project, Google SVP for technical infrastructure, Urs Hoelzle, wrote, “Last year, we crunched the numbers and found that Gmail is up to 80x more energyefficient than running traditional inhouse email … Our results show that a typical organization can achieve energy savings of about 65-85% by migrating to Google Apps …
“We found that the GSA was able to reduce server energy consumption by nearly 90% and carbon emissions by 85%. That means the GSA will save an estimated $285,000 annually on energy costs alone, a 93% cost reduction.”
Not so fast, Hoelzel, says energy expert and GreenMonk blog writer Tom Raferty. The truth may not be so simple, and statistics fog may hide some other important considerations.
First, the GSA opted to farm out all computing to Google. The agency choose to not update its own servers and data centers. However, according to Raftery, a 30-percent improvement in server efficiency could have been had by simply replacing five-year-old server technology with the latest versions. Second, what is entirely missing from the above Google calculation is the cost of data transfer. For media applications, moving large files up to a cloud and down again involves three things: personnel time (transfer wait), electrical power for the local desktop/ laptop, and switches and maintaining sufficient storage in the cloud. As we’ll see, for applications that require repeated operator interaction with the data, transfer power costs are not insignificant.
A recent report from Energy Facts Weekly suggests that cloud proponents may be fudging the facts when it comes to claiming just how “green” cloud computing really is.
In an Aug. 22 report, the newsletter quoted an IEEE Proceedings paper, “Green Cloud Computing: Balancing Energy in Processing, Storage and Transport,” as saying “… under some circumstances cloud computing can consume more energy than conventional computing on a local PC.”
A pertinent question to be asked is: What are the “circumstances”? It will require a series of articles to examine more closely the claim that cloud computing is more power efficient and therefore more environmental friendly. Figure 1 shows that as the number of file transfers between the desktop and the cloud increases, the percentage of total power consumed in the transfer process increases.
Figure 1. Percentage of total power consumption of transport, storage, and servers of a private cloud storage service as a function of download rate.
“For a private cloud storage service,” the reports says, “at a download rate above one download per hour, servers consume 35%, storage consumes less than 7%, and the remaining 58% of total power is consumed in transport. [Emphasis added.] These results suggest that transport dominates total power consumption at high usage levels for public and private cloud storage services.
“The energy consumed in transporting data between users and the cloud is therefore an important consideration when designing an energy efficient cloud storage service. Energy consumption in servers is also an important consideration at high usage levels. The percentage of total power consumed in servers is greater in private cloud computing than that in public cloud computing. In both public and private cloud storage services, the energy consumption of storage hardware is a small percentage of total power consumption at medium and high usage levels. [Emphasis added.]
In other words, for applications where large amounts of data must move between desktop and cloud, more power is required.
Before continuing, let’s ask why wouldn’t a production facility just decide to store all of its data (video) onsite? After all, in-house is safe, accessible and controllable. But, cloud proponents say cloud storage is cheaper. Maybe not. Despite the dropping costs of MB/sq-mm of platter, servers remain expensive for numerous reasons.
“Maximum areal densities in hard disk drives (HDD) are expected to more than double during the fiveyear period from 2011 to 2016,” storage analyst Fang Zhang HIS predicts. “HDD areal densities measuring data-storage capacities are projected to climb to a maximum 1,800 Gigabits (Gb) per square inch per platter by 2016, up from 744Gb per square inch in 2011 …”
Storage will become less expensive per GB, but other environmental and workflow issues remain. So, realize that media storage cost calculations should involve more than just what it costs to buy some hard disks. There is the cost of the raw storage, then the installation and maintenance. Finally, there’s the cost of cooling.
Back to Google
All this fog means that real storage costs are difficult to calculate. While the stats promoted by Google sound impressive, Raftery notes a few holes in Google’s efficiency claims. Raftery points out that anyone replacing legacy servers with newer technology would see similar performance improvements. Second, he urges engineers to consider also the cradle-to-cradle factors in server manufacturing. Manufacturing creates its own set of carbon emissions so just plugging in a newer superefficient server is not zero Co2. And, don’t forget the Co2 costs in building and operating an Exabyte-sized storage facility.
As Raftery notes in Table 2, despite Google’s claim to be zero net emissions since 2007, Google’s new GSA server farm is less Co2 efficient than the old GSA facility. While Google’s servers do produce fewer Co2 emissions per year than did GSAs, (7.69 tons versus 4.75 tons). Google’s facilities appear to be more carbon intensive (14.5 tons versus 10.63 tons). (Source: http://greenmonk.net/2012/06/21/).
Table 2. GreenMonk energy blog writer Tom Raftery has noted that Google’s new GSA server farm is less CO2 efficient than GSA’s previous facility.
The bottom line is that there are many factors to consider before jumping into the cloud. As anyone who’s actually flown through a cloud knows, the ride is often bumpy.
—Brad Dick, editorial director