Generate an energy policy tag

LSF provides esub.eas to accept the energy policy tag and the energy policy parameters.

The energy policy should minimize_energy, minimize_time or create.

esub.eas [username.]tagname policy

  • username: User generating the energy tag.
  • tagname: Maximum length of the tag name is 256 bytes. Valid characters include upper and lower case letters (a-z, A-Z), numbers (0-9), and underscore (_).
  • policy: Specify minimize_energy, minimize_time, or create

For example:

bsub –a “eas([userA.]long_running_job1, create)”

To generate a new tag, specify “create” as the second parameter. LSF will generate related data for this energy policy tag.

Note: Users can generate tags only for themselves.

The create tag job will run under the default CPU frequency and generate a tag. If there are several jobs with the same new energy tag name, the first done job will be used to generate the energy policy tag.

LSF generates the energy policy tag for a job to identify the job run time, power usage, estimated run time with other CPU frequencies and estimated performance degradation percentage.

LSF then uses a power usage and run time estimation formula to predict the job performance degradation when running with lower CPU frequencies. The power and run time predictions are based on the hardware counters LSF collected when the job ran with the default CPU frequency.

Important: Predictions require that the job run on homogenous nodes (same CPUs, same COREs, and the same amount of memory); otherwise the prediction value will be incorrect. Also, predictions can only be performed for application that make full use of the compute node - using all of the CPU power in that node and each CPU should be at about 100% CPU usage.
Note: LSF will only create the energy tag if the job runs successfully. For JOB_INCLUDE_POSTPROC=Y, the job should run post script success return JOB_STAT_PDONE. For JOB_INCLUDE_POSTPROC=N, the job should run success return JOB_STAT_DONE.
Note: When generating an energy policy tag, do not include pre/post execution commands with the job, or predictions may not be accurate.
Note: If a job has been in the UNKNOWN state, the runtime used for the tag may not be consistent with the job’s actual RUNTIME, since the sbatchd connection with mbatchd was lost and the job was finished before sbatchd could report the job was finished to mbatchd.
Note: The minimum run time for a job to generate an energy policy tag is one (1) second since the prediction runtime unit is in seconds (any job lasting less than one second will not generate a tag). Therefore, tag generation is only suitable for long running jobs. You may not receive an accurate prediction for short running jobs (several seconds).