---
title: "Tech Tip #56: Look up what your job actually used (video)"
description: "Your cluster already records the energy of every job."
url: https://greencode.ai/shorts/56-look-up-your-job-energy/
---

# Tech Tip #56: Look up what your job actually used (video)

## Tech Tip #56: Look up what your job actually used

**Your cluster already records the energy of every job.**

[Watch the video](https://media.greencode.ai/shorts/look-up-your-job-energy-02961f85ab96.mp4)

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

### The problem

Researchers see wall-clock time and core-hours, but many schedulers also record energy per job, and almost nobody looks.

### The fix you can use today

- Check whether your scheduler records job energy (for example sacct on Slurm).
- Compare energy per result between code versions and settings.
- Estimate before you run with a calculator for bigger campaigns.

The UK's ARCHER2 supercomputer lets users look up the energy of every job. GreenCode is exploring checks like this for jobs on shared clusters.

### Tools that help

- [Slurm energy accounting](https://slurm.schedmd.com/acct_gather.conf.html?utm_source=greencode.ai&utm_medium=referral&utm_campaign=greencode): records the energy each job consumed, so users can look it up after the run
- [Green Algorithms calculator](https://calculator.green-algorithms.org/?utm_source=greencode.ai&utm_medium=referral&utm_campaign=greencode): estimates the carbon footprint of a computation from its runtime, hardware and location
- [nf-co2footprint](https://nextflow-io.github.io/nf-co2footprint/?utm_source=greencode.ai&utm_medium=referral&utm_campaign=greencode): a Nextflow plugin that estimates the energy and CO2 of each task in a pipeline run

### How GreenCode helps

GreenCode helps tackle this by measuring research code's energy before and after a change, pointing to the code behind each hotspot, and checking that the optimised code still gives the same results. [More on this](https://greencode.ai/benefit/improved-scientific-computation/).

### Tags

#hpc#measurement#research-software

### Sources

- [Research software and HPC energy: ARCHER2 records energy per job](https://greencode.ai/news/research-software-hpc-energy/)
- [ARCHER2 user documentation: energy use and emissions](https://docs.archer2.ac.uk/user-guide/energy/?utm_source=greencode.ai&utm_medium=referral&utm_campaign=greencode)
- [SchedMD (Slurm), sacct manual: ConsumedEnergy field](https://slurm.schedmd.com/sacct.html?utm_source=greencode.ai&utm_medium=referral&utm_campaign=greencode)

### Transcript

Your cluster may already record the energy of every job. Researchers watch run time and core hours. But many job schedulers also record the energy each job used. And almost nobody looks. You cannot cut what you never look at. Here is the fix you can use today. First, check if your scheduler records job energy. On Slurm, energy accounting records it, and the sacct command shows it. Then compare energy per result between versions, using tools like nf-co2footprint for Nextflow. For a big campaign, estimate before you run, using the Green Algorithms calculator. The UK's ARCHER2 supercomputer lets users look up the energy of every job. GreenCode is exploring checks like this for jobs on shared clusters. GreenCode helps tackle this by measuring research code's energy before and after a change. It points to the code behind each hotspot, and checks the answers stay the same. That was GreenCode Tech Tip number fifty-six. Follow for the next tip, and find more on greencode.ai/tech-tips.

[The tip in full](https://greencode.ai/tech-tips/56-look-up-your-job-energy/)

[« Tech Tip #55: Put energy in your definition of done](https://greencode.ai/shorts/55-energy-in-definition-of-done/)[Tech Tip #57: Predict, don't just react »](https://greencode.ai/shorts/57-predictive-control-not-thresholds/)

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

#### Key Facts

- Tip **#56**
- For **Ops and infrastructure**
- Length **1:08**
- Category **HPC, embedded, mobile and games**
![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/)
