Your operating system already knows which app is draining power.
Most developers never look at energy because they think it needs lab equipment. Desktop operating systems already estimate it per application: macOS shows Energy Impact, and Windows has its Energy Estimation Engine behind its power usage views.
Microsoft and Apple build energy meters into Windows and macOS. GreenCode's research review looks at tools like these.
GreenCode helps tackle this by measuring energy before any change and after every optimisation pass, on the same machines under the same load. A saving only counts if quality, security and error rate did not get worse. More on this.
Your computer already knows which app is draining its power. Most developers never look at energy. They think it needs lab equipment. But desktop systems already estimate energy for each app. On a Mac, it is called Energy Impact. Windows has an energy estimation engine behind its power usage views. Microsoft and Apple build these energy meters into Windows and macOS. GreenCode's research review looks at tools like these. Here is the fix you can use today. Run your code, and open the Energy tab in Activity Monitor. On Windows, watch power usage in Task Manager. On Linux, try PowerTOP, or read the chip's energy counters with perf. Then compare two versions of the same task, using tools like GreenCode's green-languages. The difference matters more than the exact number. GreenCode helps tackle this by measuring energy before any change, and after every pass. A saving only counts if quality, security and errors did not get worse. That was GreenCode Tech Tip number sixty-one. Follow for the next tip, and find more on greencode.ai/tech-tips.
Share this
