Queries or removes information about the energy policy tag from the mbatchd daemon, which is saved in the energy-aware scheduling database. Used with energy policy, or energy aware scheduling feature.
Synopsisbentags [-o cpu_frequency | -o time | -o energy] [-u user | -u all] [energy_tag...]
The energy policy tag is the unique identifier of a job’s energy data, used to identify the predicted energy usage, predicted run time of the job, and the job performance degradation. The energy policy tag name is specified by using esub.eas. When you submit a job, make sure that the energy policy tag name is unique for each of your jobs.
The bentags command displays all the energy tag names that are generated by the user. When you remove an energy tag, specify the tag name or user name. If you specify the user name, all tags that belong to that user are removed. Only an LSF administrator and root can remove another user’s energy policy tags.
- Provides extended help information.
- Displays the name of the command, release number, service level, service level date, and lowest level of the operating system to run this release.
- -o cpu_frequency | time | energy
- Sort the energy tag’s data by cpu_frequency / time /
energy, in descending order. Default is to sort by CPU frequency.
cpu_frequency matches to
CPU_FREQ, time matches to
EST_RUNTIME, and energy matches to
- Remove energy policy tag. This option must be followed by the –u option or an energy tag name.
- -u user_name... | -u all
- Displays only the energy policy tags that are submitted by the specified user. The keyword all specifies all users. To specify a Windows user account, include the domain name in uppercase letters and use a single backslash (DOMAIN_NAME\user_name) in a Windows command line or a double backslash (DOMAIN_NAME\\user_name) in a UNIX command line.
- Display the data of a specific tag name.
Output: Energy tag data
- Energy Tag Name
- The energy tag name.
- Job ID
- The identifier of the job that generated the data.
- The user who generated the data.
- Default Frequency
- The CPU frequency that is used when the energy tag is generated.
- Node's Energy Use
- The direct current (DC) energy consumption per node of the job at the default frequency.
- The execution time of the job at the default frequency.
- CPU_FREQ (GHz)
- The CPU frequency.
- EST_USAGE (kWh)
- The job’s estimated DC energy consumption per host, at this frequency.
- ENER_VAR (%)
- The percentage of variation in DC energy that is consumed at this frequency. A negative value indicates the percentage of energy savings and a positive value indicates percentage of additional energy consumed.
- EST_RUNTIME (Seconds)
- The estimated run time of the job at this frequency.
- RUNTIME_VAR (%)
- The percentage of performance variation at this frequency. A negative value indicates the performance improvement and a positive value indicates the performance degradation.
- POWER (W)
- The power, measured in watts (W).
Example: Show output for tag long_running_job
bentags long_running_job Energy Tag Name: long_running_job Job ID: 526 User: UserA Default Frequency: 2.00 GHz Node's Energy Use: 0.007707 kWh Runtime: 147 Seconds CPU_FREQ(GHz) EST_USAGE(kWh) ENER_VAR(%) EST_RUNTIME(Sec) RUNTIME_VAR(%) POWER(W) 2.30 0.007582 -1.62 136 -7.48 200.70 2.20 0.007859 1.93 138 -6.12 205.03 2.10 0.007418 -3.75 140 -3.06 190.74 2.00 0.007707 0.00 147 0.00 188.74 1.90 0.007308 -5.18 144 -2.04 182.70 1.80 0.007391 -4.09 148 0.68 179.78 1.70 0.007310 -5.15 148 0.68 177.81 1.60 0.007303 -5.24 149 1.36 176.45 1.50 0.007243 -6.01 150 2.04 173.83
Example: Remove UserA.long_running_job energy policy tag from database
bentags -r UserA.long_running_job The energy policy tag <UserA.long_running_job> is removed.
Example: Remove all energy policy tags for UserA
bentags -r -u UserA The energy policy tag <UserA.long_running_job> is removed. The energy policy tag <UserA.short_running_job> is removed. The energy policy tag <UserA.medium_running_job> is removed.