{"id":18416,"date":"2020-01-17T07:03:18","date_gmt":"2020-01-17T12:03:18","guid":{"rendered":"https:\/\/www.kaspersky.co.in\/blog\/36c3-green-it\/18416\/"},"modified":"2020-03-26T19:28:05","modified_gmt":"2020-03-26T13:58:05","slug":"36c3-green-it","status":"publish","type":"post","link":"https:\/\/www.kaspersky.co.in\/blog\/36c3-green-it\/18416\/","title":{"rendered":"Going green in IT: How and why"},"content":{"rendered":"

Digital is usually perceived as nonphysical, ephemeral. However, digital services run on physical servers that require energy, and most energy is still produced by burning fossil fuels. That means digital services have a very real impact on carbon emissions and climate change. That impact, and how to minimize it, was the main topic of the talk Chris Adams of the Green Web Foundation gave at 36c3<\/a>.<\/p>\n

Big IT companies are already measuring their carbon footprints. Do you?<\/h2>\n

First let\u2019s talk numbers, looking at the biggest IT companies\u2019 impact. Amazon recently started sharing carbon emissions data<\/a>. In the year 2018, Amazon was accountable for 44.4 megatons of carbon emissions, which is as much as the country of Finland emitted that year. Most of that is third-party carbon emissions (for example, from packaging and transportation of Amazon goods, emissions from business travel, and so on).<\/p>\n

Apple had a carbon footprint of 25.2 megatons in 2018<\/a>, as much as that of Mongolia. However, if we do not count emissions from the production of Apple-branded goods, then Apple\u2019s own emissions amount to just 0.6 megatons \u2014 about as much as that year\u2019s emissions of the republic of Gambia. Half of that comes from business travel, another 30% from employees commuting. Google\u2019s carbon footprint is somewhat bigger \u2014 1.2 megatons, comparable to that of Liberia.<\/p>\n

As you can see, IT companies have a significant impact on carbon emissions. What can you do with your own IT infrastructure to minimize your impact?<\/p>\n

1. Use scalable architecture<\/h2>\n

With the rise of cloud computing, a lot of businesses started migrating their infrastructure to the cloud. But the typical approach to using cloud infrastructure involves renting an always-on server that safely exceeds the business\u2019s current peak load.<\/p>\n

However, people use the Internet \u2014 and your services \u2014 differently depending on time of day, which results in big differences in the loads. The load at night is probably significantly lower than the midday load. Analytics tools can give you a very clear understanding of how that applies to your particular services, but you get the general idea.<\/p>\n

\"Typical<\/a>

Typical distribution of Internet traffic during a day<\/p><\/div>\n

This is where scalability comes in handy. For software with scalable architecture, load balancers can automatically add more computing power on a single machine or add more servers depending on the number of requests you\u2019re receiving. That means you don\u2019t need to waste electricity \u2014 and money \u2014 on servers running in idle mode.<\/p>\n

Most cloud providers offer load balancing, both horizontal and vertical. Of course, you\u2019ll need to build your services with scalability in mind to use load balancing, but once you start, doing so will save you quite a bit of money while also lowering your cloud infrastructure\u2019s carbon footprint.<\/p>\n

2. Use greener providers<\/h2>\n

Cloud providers differ in their energy supplies. First of all, their choices may depend on the general state of electric services in the region. Some regions \u2014 for example, Sweden \u2014 rely mostly on renewable energy sources such as wind and water. Some, such as France, heavily employ nuclear power, which is also a greener choice. And some, such as Poland, get most of their energy burning coal.<\/p>\n

So, your company\u2019s carbon emissions vary depending on the location of the data center that provides its cloud computing. Bigger services such as AWS and Microsoft Azure usually pay more attention than smaller ones to that aspect of ecological sustainability.<\/p>\n

For example, Amazon Web Services users can choose the physical location of their computing power, and there\u2019s a map illustrating which of AWS\u2019s data centers run on green energy and which do not.<\/p>\n

\"AWS<\/a>

AWS regions. The green leaf means green power. Image source<\/a><\/p><\/div>\n

Microsoft, together with a group of scientists, has even built a low-carbon Kubernetes scheduler<\/a> that basically helps dynamically migrate your tasks to data centers across the globe to increase use of greener power and minimize your carbon footprint. The scheduler can be ported to work with other cloud providers as well.<\/p>\n

You don\u2019t necessarily need to choose AWS or Azure if you want to go green. The Green Web Foundation offers a directory<\/a> of smaller providers that rely on green energy. Running your computing on your own hardware is usually worse from an ecological perspective, though; cloud systems allow for a more even distribution of tasks among computing powers, helping conserve energy.<\/p>\n

3. Choose your programming language wisely<\/h2>\n

Programming languages differ in quite a few aspects including logic, syntax, capabilities, and more. They also differ in terms of resource consumption. Scripts in languages such as JavaScript and Python tend to consume more resources than compiled programs written in languages such as Fortran, C++, and Rust. And object-oriented languages, in turn, consume more than imperative ones. More resources means more power means more emissions.<\/p>\n

It\u2019s worth noting, however, that faster<\/em> doesn\u2019t necessarily mean greener<\/em>. In some cases, a program may be executed for longer but consume less energy. To learn more about languages that are time-, memory-, and energy-efficient, you can read this paper<\/a>.<\/p>\n

\"Languages<\/a>

Languages optimal for different objectives. Source<\/a><\/p><\/div>\n

Of course, you are more likely to choose programming languages for the tasks they perform, based on the abilities of your workforce, and according to the rest of your technological stack, but it\u2019s worth taking the power aspect into account; programs written in, say, JavaScript may consume twice the computing resources of those written in C.<\/p>\n

It should go without saying that optimizing the code can help lower your carbon footprint as well as make your code faster and less power-hungry, no matter the language. Profiling your software and rewriting ineffective parts can have a significant impact.<\/p>\n

4. Optimize your Web pages<\/h2>\n

Recently, the size of the average Web page exceeded that of the original Doom<\/em> download: more than 3 megabytes. The bigger the page, the more power needed to transfer it from server to the client and to display it on the client. You may think that doesn\u2019t account for a huge part of carbon emissions, but the Green Web Foundation disagrees.<\/p>\n

For example, Green Web found that running a background video on a Web page resulted in as much carbon as emitted by the project team\u2019s commutes. Remember that 30% of Apple\u2019s total emissions come from its workers\u2019 commutes? Now you see the scale.<\/p>\n

Let\u2019s add another comparison: Videos streamed over the Internet account for the same carbon footprint as the country of Spain. (The cherry on top: Porn accounts for 27% of it, or Austria\u2019s emissions.) So, point zero of optimizing is not playing videos automatically.<\/p>\n

You can use a variety of tools for optimization. Google Lighthouse<\/a> is a good example. It scores your website on four measures: performance optimization, accessibility, using best practices, and SEO optimization. Actually, performance involves all aspects, including search engine rankings and bounce rate.<\/p>\n

The Green Web Foundation has introduced another tool, called Greenhouse<\/a>, that analyzes pages and checks which of the domains they use run on renewable energy. It\u2019s not as useful as Lighthouse in terms of optimization, but it may help ecologically savvy organizations choose service providers.<\/p>\n

You can use The Green Web App<\/a> to check if your site is hosted on a server that runs on green energy. Unfortunately, not many hosting providers publish information about the greenness of the electricity they use, so your site will probably end up in gray, which simply means the foundation doesn\u2019t have the relevant information about your hosting provider.<\/p>\n

Save the planet while saving money<\/h2>\n

For some people and organizations, trying to prevent global warming is a compelling enough reason to bother with all these optimizations. But for many others, it\u2019s not. However, when it comes to IT, going green usually means saving money as well.<\/p>\n

In case the idea of saving the planet doesn\u2019t do the job, here are some more benefits of going green that may help persuade your boss:<\/p>\n

    \n
  • After optimizing your hosting and code you will need less computing power, so you\u2019ll save money on that.<\/li>\n
  • Your website will load faster, too, which means fewer customers closing it before it can fully load.<\/li>\n
  • The faster the website is, the higher search engines rank it, putting it where more customers will see it.<\/li>\n<\/ul>\n\n","protected":false},"excerpt":{"rendered":"

    Four steps to reduce your company\u2019s IT carbon footprint \u2014 and save money.<\/p>\n","protected":false},"author":675,"featured_media":18423,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[2036,2610],"tags":[2864,2333,2334,2870,2031],"class_list":{"0":"post-18416","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-business","8":"category-smb","9":"tag-36c3","10":"tag-ccc","11":"tag-chaos-communication-congress","12":"tag-ecology","13":"tag-infrastructure"},"hreflang":[{"hreflang":"en-in","url":"https:\/\/www.kaspersky.co.in\/blog\/36c3-green-it\/18416\/"},{"hreflang":"en-ae","url":"https:\/\/me-en.kaspersky.com\/blog\/36c3-green-it\/15288\/"},{"hreflang":"ar","url":"https:\/\/me.kaspersky.com\/blog\/36c3-green-it\/7377\/"},{"hreflang":"en-us","url":"https:\/\/usa.kaspersky.com\/blog\/36c3-green-it\/20174\/"},{"hreflang":"en-gb","url":"https:\/\/www.kaspersky.co.uk\/blog\/36c3-green-it\/18475\/"},{"hreflang":"es-mx","url":"https:\/\/latam.kaspersky.com\/blog\/36c3-green-it\/16909\/"},{"hreflang":"es","url":"https:\/\/www.kaspersky.es\/blog\/36c3-green-it\/20922\/"},{"hreflang":"it","url":"https:\/\/www.kaspersky.it\/blog\/36c3-green-it\/19684\/"},{"hreflang":"ru","url":"https:\/\/www.kaspersky.ru\/blog\/36c3-green-it\/26132\/"},{"hreflang":"tr","url":"https:\/\/www.kaspersky.com.tr\/blog\/36c3-green-it\/7568\/"},{"hreflang":"x-default","url":"https:\/\/www.kaspersky.com\/blog\/36c3-green-it\/32094\/"},{"hreflang":"fr","url":"https:\/\/www.kaspersky.fr\/blog\/36c3-green-it\/13618\/"},{"hreflang":"pt-br","url":"https:\/\/www.kaspersky.com.br\/blog\/36c3-green-it\/13901\/"},{"hreflang":"pl","url":"https:\/\/plblog.kaspersky.com\/36c3-green-it\/12657\/"},{"hreflang":"de","url":"https:\/\/www.kaspersky.de\/blog\/36c3-green-it\/21915\/"},{"hreflang":"zh","url":"https:\/\/www.kaspersky.com.cn\/blog\/36c3-green-it\/10648\/"},{"hreflang":"ja","url":"https:\/\/blog.kaspersky.co.jp\/36c3-green-it\/26719\/"},{"hreflang":"nl","url":"https:\/\/www.kaspersky.nl\/blog\/36c3-green-it\/24866\/"},{"hreflang":"ru-kz","url":"https:\/\/blog.kaspersky.kz\/36c3-green-it\/20857\/"},{"hreflang":"en-au","url":"https:\/\/www.kaspersky.com.au\/blog\/36c3-green-it\/25699\/"},{"hreflang":"en-za","url":"https:\/\/www.kaspersky.co.za\/blog\/36c3-green-it\/25530\/"}],"acf":[],"banners":"","maintag":{"url":"https:\/\/www.kaspersky.co.in\/blog\/tag\/36c3\/","name":"36c3"},"_links":{"self":[{"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/posts\/18416","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/users\/675"}],"replies":[{"embeddable":true,"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/comments?post=18416"}],"version-history":[{"count":7,"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/posts\/18416\/revisions"}],"predecessor-version":[{"id":19690,"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/posts\/18416\/revisions\/19690"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/media\/18423"}],"wp:attachment":[{"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/media?parent=18416"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/categories?post=18416"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/tags?post=18416"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}