---
title: "Tech Tip #41: Optimise what runs everywhere (video)"
description: "Install base, not percentage, is the number that matters."
url: https://greencode.ai/shorts/41-install-base-is-the-multiplier/
---

# Tech Tip #41: Optimise what runs everywhere (video)

## Tech Tip #41: Optimise what runs everywhere

**Install base, not percentage, is the number that matters.**

[Watch the video](https://media.greencode.ai/shorts/install-base-is-the-multiplier-6000d48cd220.mp4)

Video created by [explainapaper.com](https://explainapaper.com/?utm_source=greencode.ai&utm_medium=film&utm_campaign=made-by)

### The problem

Teams pick optimisation targets by what annoys them, not by where the energy is. A small saving in software running on millions of machines beats a big saving in a tool run once a month.

### The fix you can use today

- List systems by instances deployed and hours run.
- Prioritise high-deployment, always-on code.
- Contribute fixes upstream to open-source you depend on, so every install gains.

GreenCode's climate case shows that a saving counts again on every machine that runs the code.

### Tools that help

- [cloc](https://github.com/AlDanial/cloc?utm_source=greencode.ai&utm_medium=referral&utm_campaign=greencode): counts lines of code by language, a quick way to size a codebase
- [Software Carbon Intensity (SCI)](https://sci.greensoftware.foundation/?utm_source=greencode.ai&utm_medium=referral&utm_campaign=greencode) (Green Software Foundation): the Green Software Foundation's method, SCI = ((E x I) + M) per R, adopted as ISO/IEC 21031:2024

### How GreenCode helps

GreenCode helps tackle this by weighing each system by its install base, not just its size, so a saving is counted on every copy. Its reports show where capacity can be retired, so the saving is banked rather than spent. [More on this](https://greencode.ai/climate-case/).

### Tags

#governance#cost

### Sources

- [Decarbonising computing at scale: why deployment count is the multiplier](https://greencode.ai/decarbonising-computing-at-scale/)
- [The climate case: what one optimisation is worth](https://greencode.ai/climate-case/)

### Transcript

Install base, not percentage, is the number that matters. Teams often pick what to optimise by what annoys them. Not by where the energy goes. A small saving on millions of machines beats a big saving on one. Especially if that one tool runs once a month. An optimised release cuts energy from the day it deploys, on every copy. Here is the fix you can use today. List your systems by how many copies are deployed, and hours run. Tools like cloc give a quick size for each codebase. Then score carbon per unit of work, using the Software Carbon Intensity method. Put code that runs everywhere, all the time, first. Send fixes back to the open-source projects you depend on. Then every install gains. GreenCode's climate case shows a saving counts again on every machine running the code. GreenCode helps tackle this by weighing each system's install base, not just its code. Its reports show where capacity can be retired, so the saving is banked. That was GreenCode Tech Tip number forty-one. Follow for the next tip, and find more on greencode.ai/tech-tips.

[The tip in full](https://greencode.ai/tech-tips/41-install-base-is-the-multiplier/)

[« Tech Tip #40: Give your AI assistant structure, not raw files](https://greencode.ai/shorts/40-structured-context-for-ai/)[Tech Tip #42: Serve images at the size they're shown »](https://greencode.ai/shorts/42-size-images-for-the-screen/)

[All GreenCode Tech Tips](https://greencode.ai/tech-tips/) · [All GreenCode videos](https://greencode.ai/videos/)

#### Key Facts

- Tip **#41**
- For **CTOs and technical leads**
- Length **1:10**
- Category **Strategy, reporting and procurement**
![GreenCode](https://greencode.ai/wp-content/uploads/2024/12/greencode-logo-website-small-colours-2.webp)

Want this checked on your own system? Talk to the GreenCode team.

[Get in touch](https://greencode.ai/contact/)
