WEBVTT

1
00:00:03.850 --> 00:00:10.905
Every line of code that runs costs electricity: as a hosting bill and a cooling load, or as battery drain and heat.

2
00:00:10.905 --> 00:00:16.036
The sector's footprint is comparable to aviation's, and energy use is the largest part of it.

3
00:00:16.036 --> 00:00:20.526
A computer or server can only be as energy efficient as its software allows.

4
00:00:20.526 --> 00:00:30.788
The software is the root cause, and it has mostly been treated as a black box: the code, the architecture, the infrastructure it runs on, and the legacy systems nobody has profiled.

5
00:00:32.388 --> 00:00:41.698
GreenCode treats energy the way a mature engineering team handles quality, security or performance: something to measure, improve and verify, rather than estimate.

6
00:00:41.698 --> 00:00:49.793
First a quality baseline: the codebase is indexed, missing documentation and tests are generated, and quality flaws are refactored out.

7
00:00:49.793 --> 00:00:59.507
Then energy: the application is deployed on a reconstruction of its own infrastructure, stress-tested and benchmarked, and specialised generative AI refactors the areas responsible.

8
00:00:59.507 --> 00:01:12.460
The loop repeats until the measured improvement is good enough, and the optimised code comes back on a branch for human review, with a report on what changed and what it saved.

9
00:01:14.060 --> 00:01:24.802
What distinguishes this from a generic performance tune is when energy is recorded: before any change, after the quality baseline, and after each optimisation pass, all in the same environment.

10
00:01:24.802 --> 00:01:34.469
The headline target is a net saving per product large enough that its owners see commercial value, with quality, maintainability and security scores that must not regress.

11
00:01:36.069 --> 00:01:39.482
It is being measured on real enterprise systems.

12
00:01:39.482 --> 00:01:47.587
Transaction processing in banking and insurance, where transaction volumes are so high that even small improvements become significant savings.

13
00:01:47.587 --> 00:01:56.120
A content platform that runs nearly half of all websites, so an optimisation found once is multiplied across every installation.

14
00:01:56.120 --> 00:02:01.239
The direct power draw of optimised software in an operational data centre.

15
00:02:01.239 --> 00:02:07.638
And the processor, memory and disk demand of database servers, so that capacity matches need.

16
00:02:09.238 --> 00:02:17.523
For a legacy estate, and most software in service is exactly that, this is the low-hanging fruit: systems never designed with energy in mind, running continuously.

17
00:02:17.523 --> 00:02:18.479
The saving compounds.

18
00:02:18.479 --> 00:02:25.490
Software that needs less compute runs on less hardware, generates less heat, and extends the life of the devices it sits on.

19
00:02:25.490 --> 00:02:30.588
It is also cheaper to host, which is usually the argument that gets the work approved.

20
00:02:30.588 --> 00:02:39.511
Reach out to us with the system whose energy bill you are trying to cut, and we will help you understand how much GreenCode can take off it.
