Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • EAR EAR
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • EAR_teamEAR_team
  • EAREAR
  • Wiki
  • EAR commands

EAR commands · Changes

Page history
Updated EAR-commands.md (markdown) authored Jun 02, 2025 by Anonymous's avatar Anonymous
Show whitespace changes
Inline Side-by-side
EAR-commands.md
View page @ f81b46ba
...@@ -6,7 +6,7 @@ EAR offers a set of commands which help both users and administrators to interac ...@@ -6,7 +6,7 @@ EAR offers a set of commands which help both users and administrators to interac
- A command to load transparently the EAR Library on systems where the batch scheduler has not a plug-in nor some use case isn't supported (e.g., running an OpenMPI application on SLURM systems through the `mpirun` command): [erun](#erun). - A command to load transparently the EAR Library on systems where the batch scheduler has not a plug-in nor some use case isn't supported (e.g., running an OpenMPI application on SLURM systems through the `mpirun` command): [erun](#erun).
- A command to show current EAR installation information: [ear-info](#ear-info). - A command to show current EAR installation information: [ear-info](#ear-info).
Commands belonging to the first three categories read the EAR configurarion file Commands belonging to the first three categories read the EAR configuration file
(`ear.conf`) to determine whether the user is authorized, as some of them has some (`ear.conf`) to determine whether the user is authorized, as some of them has some
features (or the wall command) only available that set of users. features (or the wall command) only available that set of users.
Root is a special case, it doesn't need to be included in the list of authorized users. Root is a special case, it doesn't need to be included in the list of authorized users.
...@@ -37,7 +37,7 @@ It provides the following options. ...@@ -37,7 +37,7 @@ It provides the following options.
-s specifies the minimum start time of the jobs that will be retrieved in YYYY-MM-DD. [default: no filter]. -s specifies the minimum start time of the jobs that will be retrieved in YYYY-MM-DD. [default: no filter].
-e specifies the maximum end time of the jobs that will be retrieved in YYYY-MM-DD. [default: no filter]. -e specifies the maximum end time of the jobs that will be retrieved in YYYY-MM-DD. [default: no filter].
-l shows the information for each node for each job instead of the global statistics for said job. -l shows the information for each node for each job instead of the global statistics for said job.
-x shows the last EAR events. Nodes, job ids, and step ids can be specified as if were showing job information. -x shows the last EAR events. Nodes, job ids, and step ids can be specified as if it were showing job information.
-m prints power signatures regardless of whether mpi signatures are available or not. -m prints power signatures regardless of whether mpi signatures are available or not.
-r shows the EAR loop signatures. Nodes, job ids, and step ids can be specified as if were showing job information. -r shows the EAR loop signatures. Nodes, job ids, and step ids can be specified as if were showing job information.
-o modifies the -r option to also show the corresponding jobs. Should be used with -j. -o modifies the -r option to also show the corresponding jobs. Should be used with -j.
...@@ -92,7 +92,7 @@ If EAR supports GPU monitoring/optimisation, the following columns are added: ...@@ -92,7 +92,7 @@ If EAR supports GPU monitoring/optimisation, the following columns are added:
For node-specific information, the `-l` (i.e., long) option provides detailed accounting of each individual node. For node-specific information, the `-l` (i.e., long) option provides detailed accounting of each individual node.
In addition, `eacct` shows an additional column: `VPI(%)`. In addition, `eacct` shows an additional column: `VPI(%)`.
The VPI is meaning the percentage of AVX512 instructions over the total number of instructions. The VPI means the percentage of AVX512 instructions over the total number of instructions.
For runtime data (EAR loops) one may retrieve them with `-r`. For runtime data (EAR loops) one may retrieve them with `-r`.
Both Job and Step ID filtering works. Both Job and Step ID filtering works.
...@@ -363,7 +363,7 @@ Creates the EAR DB used for accounting and for the global energy control. Requir ...@@ -363,7 +363,7 @@ Creates the EAR DB used for accounting and for the global energy control. Requir
Usage:edb_create [options] Usage:edb_create [options]
-p Specify the password for MySQL's root user. -p Specify the password for MySQL's root user.
-o Outputs the commands that would run. -o Outputs the commands that would run.
-r Runs the program. If '-o' this option will be override. -r Runs the program. If '-o' this option will be overriden.
-h Shows this message. -h Shows this message.
``` ```
...@@ -373,7 +373,7 @@ Cleans periodic metrics from the database. Used to reduce the size of EAR's data ...@@ -373,7 +373,7 @@ Cleans periodic metrics from the database. Used to reduce the size of EAR's data
``` ```
Usage:./src/commands/edb_clean_pm [options] Usage:./src/commands/edb_clean_pm [options]
-d num_days REQUIRED: Specify how many days will be kept in database. (defaut: 0 days). -d num_days REQUIRED: Specify how many days will be kept in database. (default: 0 days).
-p Specify the password for MySQL's root user. -p Specify the password for MySQL's root user.
-o Print the query instead of running it (default: off). -o Print the query instead of running it (default: off).
-r Execute the query (default: on). -r Execute the query (default: on).
......
Clone repository
  • Home
  • User guide
    • Use cases
      • MPI applications
      • Non-MPI applications
      • Other use cases
      • Usage inside Singularity containers
      • Usage through the COMPSs Framework
    • EAR data
      • Post-mortem application data
      • Runtime report plug-ins
      • EARL events
      • MPI stats
      • Paraver traces
      • Grafana
    • Submission flags
    • Examples
    • Job accounting
    • Job energy optimization
  • Tutorials
  • Commands
    • Job accounting (eacct)
    • System energy report (ereport)
    • EAR control (econtrol)
    • Database management
    • erun
    • ear-info
  • Environment variables
    • Support for Intel(R) speed select technology
  • Admin Guide
    • Quick installation guide
    • Installation from RPM
    • Updating
  • Installation from source
  • Architecture/Services
  • High Availability support
  • Configuration
  • Learning phase
  • Plug-ins
  • Powercap
  • Report plug-ins
  • Database
    • Updating the database from previous EAR versions
    • Tables description
  • Supported systems
  • EAR Data Center Monitoring
  • CHANGELOG
  • FAQs
  • Known issues