That instance at 3% CPU has been running for a year.
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.
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.
That server at three percent busy has been running for a year. Test systems, forgotten servers, old disks and leftover containers keep running. Often, the project they served finished long ago. Nobody owns them, so nobody turns them off. They rarely show up in performance reviews. Only on the bill. They use energy and money, and produce nothing. Here is the fix you can use today. List everything with low processor and network use, over a long time. One rule: under ten percent processor, and under five megabytes a second of network. Tag every resource with an owner and an expiry date. Delete what nobody claims, or stop it out of hours. The Green Software Foundation suggests removing unused assets. GreenCode takes this into account. GreenCode's Constitution skill can help an AI coding agent spot idle resources. Then check their energy and emissions, using tools like Cloud Carbon Footprint and Kepler. GreenCode helps tackle this by mapping your running systems and the energy each one uses. It shows which services run hot, and which barely run at all. That was GreenCode Tech Tip number twenty-one. Follow for the next tip, and find more on greencode.ai/tech-tips.
Share this