---
title: "Tech Tip #2: Your cloud servers are mostly idle (video)"
description: "Most cloud servers sit idle about seventy percent of the time."
url: https://greencode.ai/shorts/2-your-cloud-servers-are-mostly-idle/
---

# Tech Tip #2: Your cloud servers are mostly idle (video)

## Tech Tip #2: Your cloud servers are mostly idle

**Most cloud servers sit idle about seventy percent of the time.**

[Watch the video](https://media.greencode.ai/shorts/your-cloud-servers-are-mostly-idle-267336d4a23c.mp4)

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

### The problem

Published studies put cloud servers active only 10 to 30% of the time, yet an idle machine still draws a significant fraction of its peak power. Servers are bought for the busiest moment, and slow software makes that moment bigger than it needs to be.

### The fix you can use today

- First cut the load: fix the wasteful code so each request needs less.
- Then right-size: fewer or smaller machines for what is left.
- Let quiet services scale to zero, and look for machines idle all day.

Studies reviewed by GreenCode researchers found that many cloud servers are busy only 10 to 30% of the time. GreenCode's research review draws on this work.

### Tools that help

- [GreenCode Constitution skill](https://greencode-constitution.org/?utm_source=greencode.ai&utm_medium=referral&utm_campaign=greencode) (GreenCode researchers): open-source energy principles and a catalogue of 37 energy anti-patterns that an AI coding agent can follow to find and fix waste like this
- [Scaphandre](https://github.com/hubblo-org/scaphandre?utm_source=greencode.ai&utm_medium=referral&utm_campaign=greencode): measures the power drawn by each process on a Linux server and exports it to Prometheus and other monitoring stacks
- [Kepler](https://github.com/sustainable-computing-io/kepler?utm_source=greencode.ai&utm_medium=referral&utm_campaign=greencode): exports energy estimates per pod and container on Kubernetes, using eBPF and hardware counters

### How GreenCode helps

GreenCode helps tackle this by mapping a running estate and tracing its energy and CO2e to the services that cause it. That shows which services run hot and which are barely running at all. [More on this](https://greencode.ai/feature/infrastructure-carbon-footprint-assessment/).

### Tags

#idle#right-sizing#cloud#cost

### Sources

- [Reduced infrastructure requirements (servers active 10 to 30% of the time)](https://greencode.ai/benefit/reduced-infrastrcuture-requirements/)
- [GreenCode State of the Art Review, D2.1 (2025), PDF p. 16: idle power draw often a significant fraction of peak; consolidation and right-sizing as levers](https://greencode.ai/publications/d2-1-state-of-the-art-review/)
- [GreenCode State of the Art Review, D2.1 (2025), PDF p. 68: cloud servers active only 10-30% of the time, idle around 70%](https://greencode.ai/publications/d2-1-state-of-the-art-review/)
- [Green Software Foundation, Green Software Patterns: match utilisation requirements with pre-configured servers](https://github.com/Green-Software-Foundation/patterns/blob/main/docs/operations/capacity-management/match-utilization-requirements-with-pre-configured-server.md?utm_source=greencode.ai&utm_medium=referral&utm_campaign=greencode)
- [Green Software Foundation, Green Software Patterns: scale infrastructure with user load](https://github.com/Green-Software-Foundation/patterns/blob/main/docs/operations/capacity-management/scale-infrastructure-with-user-load.md?utm_source=greencode.ai&utm_medium=referral&utm_campaign=greencode)
- [W3C, Web Sustainability Guidelines: reduce allocated capacity when consistently underused; autoscale](https://www.w3.org/TR/web-sustainability-guidelines/#automated-scaling)

### Transcript

Most cloud servers sit idle about seventy percent of the time. They are busy only ten to thirty percent of the time. That comes from studies reviewed by GreenCode researchers. GreenCode's research review draws on this work. But idle machines still draw a big share of their full power. Servers are bought for the busiest moment, and slow software makes that moment bigger. So you pay for electricity, cooling and hardware that mostly wait. Here is the fix you can use today, in the right order. First, cut the load, by fixing the wasteful code. Then right-size: fewer or smaller machines for what is left. And let quiet services scale down to zero. Check your dashboards for machines that are mostly idle, all day. Kepler shows each Kubernetes pod's energy; Cloud Carbon Footprint estimates yours from cloud bills. Shrink the machines first, and you just size them for the waste. GreenCode helps tackle this by tracing energy and carbon to the services that cause it. That shows which services run hot, and which barely run at all. That was GreenCode Tech Tip number two. Follow for the next tip, and find more on greencode.ai/tech-tips.

[The tip in full](https://greencode.ai/tech-tips/2-your-cloud-servers-are-mostly-idle/)

[« Tech Tip #1: Stop the N+1 query](https://greencode.ai/shorts/1-stop-the-n-plus-one-query/)[Tech Tip #3: Measure before and after, on the same setup »](https://greencode.ai/shorts/3-measure-before-and-after/)

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

#### Key Facts

- Tip **#2**
- For **Ops and infrastructure**
- Length **1:12**
- Category **Cloud and infrastructure**
![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/)
