---
title: "Tech Tip #21: Find and remove zombie resources"
description: "That instance at 3% CPU has been running for a year."
url: https://greencode.ai/tech-tips/21-remove-zombie-resources/
---

# Tech Tip #21: Find and remove zombie resources

**That instance at 3% CPU has been running for a year.**

[Watch the video](https://media.greencode.ai/shorts/remove-zombie-resources-245b792cf200.mp4)

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

### The problem

Test environments, forgotten VMs, orphaned volumes and pods from finished projects keep running because nobody owns them. They rarely show up in performance reviews, only on the bill.

### The fix you can use today

- List everything with sustained low CPU and network use (the Constitution uses under 10% CPU and under 5 MB/s network).
- Tag every resource with an owner and an expiry date.
- Delete, or schedule to stop out of hours, what nobody claims.

### 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
- [Cloud Carbon Footprint](https://www.cloudcarbonfootprint.org/?utm_source=greencode.ai&utm_medium=referral&utm_campaign=greencode): estimates the energy and emissions of AWS, Azure and Google Cloud usage from billing and usage data
- [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 the energy each service uses. It shows which services run hot and which barely run at all. [More on this](https://greencode.ai/feature/infrastructure-carbon-footprint-assessment/).

### Tags

#idle#cloud#cost

### Sources

- [GreenCode Constitution skill, energy anti-patterns: C7 idle cloud resources: sustained <10% CPU and <5 MB/s network I/O (Tier 1)](https://greencode-constitution.org/skill.md?utm_source=greencode.ai&utm_medium=referral&utm_campaign=greencode)
- [Green Software Foundation, Green Software Patterns: Remove unused assets](https://github.com/Green-Software-Foundation/patterns/blob/main/docs/operations/resource-lifecycle/remove-unused-assets.md?utm_source=greencode.ai&utm_medium=referral&utm_campaign=greencode)
- [Microsoft, Azure Well-Architected sustainability (Reliability): remove zombie workloads and orphaned resources](https://learn.microsoft.com/en-us/azure/well-architected/sustainability/sustainability-reliability-recommendations?utm_source=greencode.ai&utm_medium=referral&utm_campaign=greencode)
- [W3C, Web Sustainability Guidelines: remove unused environments and right-size allocations](https://www.w3.org/TR/web-sustainability-guidelines/#unused-environments)

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

#### Key Facts

- Tip **#21**
- For **Ops and infrastructure**
- Category **Cloud and infrastructure**
- 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/)
