---
title: "Tech Tip #12: Faster is not always greener"
description: "Your speed-up might not save the energy you think."
url: https://greencode.ai/tech-tips/12-faster-is-not-always-greener/
---

# Tech Tip #12: Faster is not always greener

**Your speed-up might not save the energy you think.**

[Watch the video](https://media.greencode.ai/shorts/faster-is-not-always-greener-f3af74196f32.mp4)

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

### The problem

Teams treat speed as a stand-in for energy, but the two do not move together. On llama.cpp, GreenCode research cut GPU energy by 4.7% while speed rose only 3%: energy and time told different stories.

### The fix you can use today

- Measure energy directly, not only runtime.
- Compare before and after on the same machine under the same load.
- Report both numbers; a change can be faster and hungrier, or slower and leaner.

GreenCode researchers found that speed gains and energy savings are not the same thing, so they measure both.

### Tools that help

- [green-languages](https://github.com/PLEnergyDev/green-languages?utm_source=greencode.ai&utm_medium=referral&utm_campaign=greencode) (GreenCode researchers): a command-line tool that measures the energy of whole programs or marked sections of code, across languages
- [GreenCode Constitution profiler (profile.sh)](https://greencode-constitution.org/skill.md?utm_source=greencode.ai&utm_medium=referral&utm_campaign=greencode) (GreenCode researchers): a script from the Constitution tooling that measures the energy of a command from processor counters, GPU sensors and an optional smart plug, and writes the result as JSON
- [perf (RAPL counters)](https://perfwiki.github.io/main/?utm_source=greencode.ai&utm_medium=referral&utm_campaign=greencode): Linux perf reads the processor's RAPL energy counters, e.g. `perf stat -e power/energy-pkg/`

### How GreenCode helps

GreenCode helps tackle this by running a load test built from your system's own endpoints. It records energy as well as speed, and ranks the hotspots by the energy they use. [More on this](https://greencode.ai/feature/automated-performance-testing/).

### Tags

#measurement#profiling#llm#gpu

### Sources

- [GreenCode Constitution (Kapenekakis et al., GreenAI workshop, ECML PKDD 2026): llama.cpp: 4.7% GPU energy saved (3.7% in total) against a 3% speed gain](https://greencode.ai/publications/greencode-constitution-agent-principles-for-optimizing-code-and-llm-inference-en/)
- [Green AI is a mathematics problem as much as a hardware one](https://greencode.ai/news/mathematics-and-green-ai/)

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

#### Key Facts

- Tip **#12**
- For **Developers**
- Category **Measuring energy**
- Format **short video**
![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/)
