Kate's Comment

Thoughts on British ICT, energy & environment, cloud computing and security from Memset's MD

Energy of downloads

The music and movies industry are keen to tell us how enormously energy intensive downloading media can be. But just how much energy does get used when you download stuff from the Internet? I plugged some numbers from our data centre into my calculator to find out!

I started with calculations based on our own power consumption (servers and in-datacentre network gear) and bandwidth output. We measure all power consumption and network activity, so all I had to do was design queries for our master data base.

Sampling one of our data centre suite’s energy consumption and bandwidth output, and dividing the former by the latter, gives a figure of 2.58 Watt-hours (Wh) per Megabyte (MB). That suite is our newest, and contains a mixture of Web hosting, application hosting, storage and other services. Some servers are used inefficiently at low utilisation, and some very efficiently, notable those which are part of our Miniserver VM® grid.

For example, if we restrict the data to that from a selection of ten of our latest Miniserver VM® host servers (quad-core 1U Dell Power Edge servers stuffed with RAM) the figure is only 0.61 Wh/MB, but I’m trying to be conservative here and make the calculations applicable to any Web-delivered service, not just the efficiently-run ones.

We must not forget the cooling and infrastructure losses (UPS, wiring etc). Our power usage efficacy (PUE) is about 1.4, but let’s err on the side of caution and add 50%, giving a total for electricity requirements at the data centre of 3.87 Wh/MB.

My educated guess of a typical 1U server’s embedded energy is 1,000 kWh (explanation here). If we assume a 3 year lifespan (it is actually more like 4-5 years in our case) then we get 333 kWh/year. Such a server uses about 100Watts continuously, or 1,100 kWh/year, so applying that ratio (1,100:333 = 3.3:1) we get an embedded energy cost of 0.78 Wh/MB.

The network and firewall boxes are probably in the same ball park in terms of embedded energy, however compared to servers there are very few of them: 1 switch per 30 servers, 1 router-firewall pair per ~200-500 servers, 1 border router pair per 2,000-20,000 servers. Therefore that equipment’s embedded energy is not significant in our sums. The same goes for the embedded energy of the data centre itself; when compared to the thousands of servers housed within, it rapidly becomes an insignificant factor. Rather than ignore it entirely, however, I shall add 10% to the embedded server energy factor (0.86 Wh/MB total) as an allowance for the embedded energy of the supporting infrastructure.

After some conversation with ISP friends we decided that the only really significant part of the network delivery energy will be the end points. Even though some big core routers consume kilo-Watts, they are shunting hundreds of gigabits per second, thus their power requirements are spread over a huge aggregation of data flows and rendered insignificant. The end points are the Digital Subscriber Line Access Multiplexers (DSLAMs – the big modems that send an ADSL signal down your phone line), and power for the home phone line itself.

According to the EU code of conduct for broadband equipment DSLAMs with more than 100 ports should use no more than about 1.3 Watts per port when active, so a fair high estimate of their average usage would be 1Watt. The phone line is a bit more difficult to estimate, but with my rudimentary knowledge of electrical systems and telecommunications equipment I think an upper estimate of 2 Watts is reasonable. Counting the phone line, and even the DSLAM, may seem a bit pointless since they are likely to be there anyway, but we are aiming to illuminate a worst-case scenario (ie. someone who otherwise would not have the phone line).

Anyway, if counting them, then we have, say, 3 Watts continuous (2,190 Wh) which gets used for about 2GBytes per month (a low average usage estimate, but in line with many ISP’s fair usage policies), which gives another 1.09 Wh/MB.

So, to sum up:

Servers & networking kit: 2.6 Wh/MB
Data centre cooling & losses: 1.3 Wh/MB
Embedded kit energy: 0.9 Wh/MB
DSLAMs & phone line: 1.1 Wh/MB
Total: 5.9 Wh/MB

According to Google the average Web page is about 320 KBytes these days. Therefore, downloading a single Web page uses about 1.9 Wh. Boiling the water for a mug of tea in a kettle, by comparison, uses about 50 Wh (a 3KW kettle takes 90 secs to boil 2 mugs-worth – 37.5 Wh – plus a bit for the wasted water).

A music album is in the region of 100 MBytes (a bit more for iTunes, and varies depending on quality and number of tracks of course), which would be 590 Wh. A typical small electric car uses about 300 Wh per mile, so you could drive about 2 miles on the energy required to download and deliver a music album, or do the tea round for 12 people. The energy required to deliver music on CD is vastly more, of course, and I will look at that in another article, but it is interesting to see that downloading is certainly not without its carbon impact.

While the above calculations are fun it is important to point out that equating downloading to absolute energy requirements is extremely crude and should be treated with caution. A heavy Internet user would be much more efficient, for example, and the nature of the configuration of the servers in the data centre will also have a large effect, as seen with the differences if only our virtual machine grid is used in the assessment.

I also made a number of assumptions about the home end of the network, and it is useful to see the lower-end of the range. Therefore, if we use the Miniserver VM® figure of 1.22 Wh/MB (including cooling and embedded energy), assume that the DSLAM ports are efficient when idle (most of the time) and call that 0.5 Watt and that the phone line itself is just 1 Watt giving a total of 0.55 Wh/MB (the same as if we assume the average utilisation is double my estimate, at 4BGytes/month), then we get a total figure of only 1.8 Wh/MB as the lower end of our download energy estimate.

For instance, if we assume that Apple run an efficient data centre infrastructure for serving their iTunes customers with similar properties to our virtual machine grid (which is very likely), and that the above lower estimate for the phone line is accurate, then a 100MByte album from them would only take 180 Wh – or about 3.5 mugs of tea worth of energy.

On the flip side, I have not included the energy to run the home network and PC(s)/laptop(s), which many papers do, but that greatly skews the figures and we are assuming here that those bits of equipment are used for other purposes than just downloading.