Tech Tip #69: Try a lower CPU frequency for batch work

A 2 GHz cap cost 1-5% speed and saved 13-20% energy.

The problem

Processors run at maximum frequency by default, even for batch jobs where nobody is waiting for the extra few per cent of speed. Energy rises faster than speed at the top of the range.

The fix you can use today

  • Benchmark representative jobs at a lower frequency cap.
  • Make the efficient setting the default for batch queues, with an opt-out.
  • Re-check when hardware or code changes.

The team behind the UK's ARCHER2 supercomputer found that a lower CPU speed cut energy by 13 to 20% for most codes they tested. GreenCode keeps advice like this in mind in its work.

Tools that help

  • Slurm energy accounting: records the energy each job consumed, so users can look it up after the run
  • LIKWID: reads hardware performance and energy counters on HPC nodes

How GreenCode helps

GreenCode helps tackle this on the code side: it measures research code's energy before and after each change, and checks that the optimised code still gives the same results. More on this.

Tags

#hpc#hardware#scheduling

Sources

All GreenCode Tech Tips

  • Tip #69
  • For Ops and infrastructure
  • Category HPC, embedded, mobile and games
  • Format short video
GreenCode

Want this checked on your own system? Talk to the GreenCode team.

Get in touch