Green-Software-Foundation / Green-Software-Foundation/sci-guide

Measuring emissions for a large three tier, on-premise software system

Open
#42 3 comments 0 reactions 2 assignees Claimed by @ursvill View on GitHub
Use Case
Dominant language
TypeScript
Stars
9
Forks
18
PR merge metrics
No merged PRs in 30d

Description

## Executive Summary
This article describes how NTT DATA used the SCI score to help measure the carbon footprint of a large scale three-tier on premise software system

### Description of problem
There are a number of large scale multi tier, on-premise software systems being developed and maintained by NTT DATA that run enterprise scale applications such as ecommerce. While there is a desire by all enterprises to migrate to the cloud at some point in the future, there will be a considerable portfolio of on-premise solutions that we need to live with for the next few years. It is important that the carbon footprint of these applications are measured and optimised, especially as they continue to scale.

### How the use case solves the problem
NTT DATA has a mature set of tools and techniques to optimise performance of such software systems. We use industry standard benchmarks such as TPC-W which provide a benchmark for performance in terms of Web Interactions per second for a given load. We have implemented tooling across the entire stack including networking, hardware and software to measure the rate of emissions using SCI. We have measured it in term of co2 equivalent per web interaction

### Main benefits of the solution
This has helped us to gather carbon emissions related metrics , utilising some of the mature processes that we regularly perform such as the performance optimisation. This in turn helps us understand the impact of scaling the systems on the total carbon footprint and take appropriate actions to help bring down the carbon footprint

### What was the outcome, how were carbon emissions reduced
We now have a baseline for the carbon impact per unit of work , based on a blueprint infrastructure, that provides a baseline performance. We will now use this to implement patterns that decrease the carbon footprint with no negative impact on performance and also to be aware of the carbon impact on any performance improvement, scaling decision that we make on the software system

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.