{"id":52416,"date":"2021-10-12T11:00:17","date_gmt":"2021-10-12T10:00:17","guid":{"rendered":""},"modified":"2022-02-10T20:49:04","modified_gmt":"2022-02-10T19:49:04","slug":"how-to-measure-and-reduce-the-carbon-footprint-of-your-application","status":"publish","type":"post","link":"https:\/\/www.microsoft.com\/en-gb\/industry\/blog\/technetuk\/2021\/10\/12\/how-to-measure-and-reduce-the-carbon-footprint-of-your-application\/","title":{"rendered":"How to measure and reduce the carbon footprint of your application"},"content":{"rendered":"

\"An<\/p>\n

\n
\n

I\u2019m a green software engineer<\/a>, and the first principle of green software engineering is to build applications that are carbon efficient<\/strong>. That means for each gram of carbon our application is responsible for emitting into the environment, we try to extract the most value from that gram as possible.<\/p>\n

So, in this context, the first metric you might think of is carbon. And although we do need to calculate the carbon emissions of our application at some level, it\u2019s particularly hard to measure. There’s no HTTP response header that returns the carbon cost of the request (maybe there should be?), so most of what we do is try to model. When we model, we make assumptions, and those assumptions might impact where we put efforts to optimise.<\/p>\n

For example, a common challenge is the carbon intensity of electricity. Electricity is dirty and it emits carbon in its creation \u2013 how much carbon it emits is known as carbon intensity. The global<\/strong> average for carbon intensity produced in 2020 was 519g\/kWh, but each electricity grid in the world has a different number because each grid has a different mix of clean and dirty electricity sources. It also changes over time, so each minute in each region has a different carbon intensity. Which of these numbers is the right one to use when calculating your carbon metric?<\/p>\n

If you choose a global yearly average and try to save carbon by running your application in a region with cleaner electricity, that change won\u2019t be reflected in your carbon metric.<\/p>\n

If you decide to include real-time regional carbon intensity numbers in your calculation, then imagine this scenario; You release a code change and your carbon metric goes up. Did your code change make the application worse or has the electricity become dirtier? In this scenario, the real-time carbon metric is a problem as it\u2019s causing false positives.<\/p>\n

At the same time, perhaps you released a code change that shifted workloads to times and regions when the electricity was cleaner. If this was the case, then you\u2019d want your carbon metric to use real-time regional carbon intensity numbers to tell you your code change had a positive impact.<\/p>\n

It\u2019s good to attempt to model and think of the overall carbon number of your application, but be aware of how that number is being calculated and what assumptions are being made.<\/p>\n

 <\/p>\n

Look for carbon proxies<\/h3>\n

An easier solution is to look for carbon proxies.<\/strong> If you can somehow connect what you are measuring to carbon, then it\u2019s a proxy. And optimising for that metric is optimising for carbon.<\/p>\n

For example, let\u2019s take a look at electricity. We burn fossil fuels to make electricity, meaning there is a connection between electricity and carbon. This makes electricity a carbon proxy<\/strong>. Therefore, reducing the energy consumed by your application reduces the amount of carbon it\u2019s responsible for emitting.<\/p>\n

 <\/p>\n

How to choose carbon proxy metrics<\/h3>\n

The metrics you choose will open the doors to optimisations as if you measure something, you will usually aim to optimise it, so picking the right measurement criteria is key<\/strong>.<\/p>\n

Our goal as green software engineers is not to write reports, it\u2019s to implement change. We need information to know what these changes should be. When picking a carbon proxy, be less concerned about how accurately you can measure it, and more concerned about the directional information the proxy gives you. It\u2019s OK if your units are off, and it\u2019s OK if it\u2019s not accurate. As long as the metric behaves in a way that gives us the right information to make the right choices, it\u2019s good enough.<\/p>\n

What you choose to measure will impact what you will optimise, and because of the assumptions that need to be made when summarising, multiple metrics are better than one<\/strong>.<\/p>\n

Some metrics are easier to measure than others: pick what\u2019s manageable at the start, add others as you refine your green software engineering methodology.<\/p>\n

 <\/p>\n

What carbon proxy metrics should you choose for a website?<\/h3>\n

\"A<\/p>\n

Let\u2019s take a look at what metrics a website might need. We\u2019ll pick a reference architecture of a basic multi-page application (i.e. most websites). Every time a user clicks a link, the browser makes a request to the server, the server generates some HTML and returns it in the response which the browser then renders on the client machine.<\/p>\n

We have a frontend running on a client machine, some networking, and a backend running on some servers. We assume the application is not a bitcoin miner or a game \u2013 essentially once parsed and loaded in the browser, the application is not running constantly and taking up CPU.<\/p>\n

So, what are some good carbon proxy metrics we might choose to measure for this application?<\/p>\n

Frontend<\/h4>\n

For the frontend, the ideal carbon proxy would be the total energy used to render the webpage. There are tools to measure this, however, pulling that all together into an automated measurement system is not easy. Another carbon proxy we can then use is time-to-interactive<\/strong><\/a>. This is the time it takes from the response being made to the page being rendered and usable on the client device. We\u2019ll make the assumption here that the energy used is proportional to the time, though this might not always be the case.<\/p>\n

A lower time-to-interactive implies an application that:<\/p>\n