November 24, 2009
*CuttingTheBill*
Paper Title: Cutting the electric Bill for Internet-Scale Systems
Author(s): Asfandyar Qureshi, Rich Wber, Hari Balakrishnan, John Guttag,
Bruce Maggs
Date: SIGCOMM �09. August 17-21, 2009.
Novel Idea: The authors argue that cost savings in the millions of
dollars can be achieved by making data-center routing decisions based on
real-time energy costs, routing user requests to data centers which have
the lowest current cost per megawatt-hour.
Main Result(s)/Evidence: The authors use activity reports from Akami and
market pricing data from various regional ISOs to determine the cost
savings possible when using energy prices in the routing decision. The
authors find that energy elasticity has an enormous impact on
effectiveness; if idle servers consume the same amount of electricity as
loaded servers then it makes little sense to shuffle requests around.
Experiments also confirmed that cost savings could be achieved even when
bandwidth (at 95/5) and the maximum distance between client and server
are held as constraints. The authors do a good job of enumerating the
underlying assumptions to their model in their discussion.
Impact: Hard to tell; it seems intuitive to me that processing requests
in data centers with lower energy costs could save one money, at the
possible expense of bandwidth and latency.
Prior/Competitive Work: A formal discussion of prior work is notably
missing from the paper. The authors note in their introduction that
techniques which seek to reduce energy consumption (such as by
decreasing cooling costs, switching to DC power, using virtualization,
etc) are complimentary to their work.
Reproducibility: Any effort to reproduce the author�s results would
likely involve collecting utilization data from sources other than Akami
and looking for conclusions similar to those reached by the authors.
There is not much utility in reproducing the author�s experiments otherwise.
Question: The estimated energy costs cited for Google ($38M) account for
one-third of one-percent of its expenditures for 2007, or 0.22% of
revenues. Are energy costs really relevant?
[
http://investor.google.com/fin_data.html]
Criticism:
1.) Assuming that a distributed system is �fully replicated� is a bit
na�ve� We�ve read many papers this semester where the opposite is true.
For example, a user profile is stored at one primary location and
replicated only to a few others.
2.) Does this work depend too heavily on the organization of the U.S.
energy market? The trend appears to be toward unifying the power grid �
will that promote national price parity and make parts of this work
irrelevant?
3.) I�m sure is incidental, but what is the energy penalty for running
these added algorithms?
4.) The findings in this paper benefit from hindsight (�if we did X, we
would have saved Y�). The paper acknowledges that most sites hedge power
costs by buying fixed-price contracts�these contracts are in effect
�insurance policies� against potentially unbounded price increases in a
volatile market, and in turn might have a value greater than the
estimated cost savings proposed by the authors work. The paper also
side-steps the question of whether companies can achieve better cost
savings in the long-term by negotiating fixed-price contracts vs using
the proposed real-time routing techniques.
Future Work:
1.) As data centers grow, could they turn to generating some or all
their own power? I believe this is a common practice in large factories
today.
2.) Figure out how I can sign up for some of those �negative energy prices�.