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 Database

EAR Database · Changes

Page history
Update EAR Database authored Jul 20, 2023 by Lluis Alonso's avatar Lluis Alonso
Hide whitespace changes
Inline Side-by-side
EAR-Database.md
View page @ 78771b32
...@@ -78,19 +78,6 @@ Additionally, if EAR was compiled in a system with GPUs (or with the GPU flag ma ...@@ -78,19 +78,6 @@ Additionally, if EAR was compiled in a system with GPUs (or with the GPU flag ma
### From EAR 4.2 to 4.3 ### From EAR 4.2 to 4.3
To add support for workflows, a new field was added to several tables to allow their accounting:
```
ALTER TABLE Jobs ADD COLUMN local_id INT UNSIGNED NOT NULL AFTER step_id;
ALTER TABLE Jobs DROP PRIMARY KEY, ADD PRIMARY KEY (job_id, step_id, local_id);
```
```
ALTER TABLE Applications ADD COLUMN local_id INT UNSIGNED NOT NULL AFTER step_id;
ALTER TABLE Applications DROP PRIMARY KEY, ADD PRIMARY KEY (job_id, step_id, local_id);
```
```
ALTER TABLE Loops ADD COLUMN local_id INT UNSIGNED NOT NULL AFTER step_id;
```
Three new fields corresponding to L1, L2 and L3 cache misses have been added to the signatures. Three new fields corresponding to L1, L2 and L3 cache misses have been added to the signatures.
> **NOTE** This change only applies to the databases that have been created with the extended application signature (i.e. they have the FLOPS, instructions and cycles counters in their signatures). > **NOTE** This change only applies to the databases that have been created with the extended application signature (i.e. they have the FLOPS, instructions and cycles counters in their signatures).
...@@ -101,6 +88,7 @@ ADD COLUMN L1_misses BIGINT UNSIGNED AFTER perc_MPI, ...@@ -101,6 +88,7 @@ ADD COLUMN L1_misses BIGINT UNSIGNED AFTER perc_MPI,
ADD COLUMN L2_misses BIGINT UNSIGNED AFTER L1_misses, ADD COLUMN L2_misses BIGINT UNSIGNED AFTER L1_misses,
ADD COLUMN L3_misses BIGINT UNSIGNED AFTER L2_misses; ADD COLUMN L3_misses BIGINT UNSIGNED AFTER L2_misses;
``` ```
``` ```
ALTER TABLE Learning_signatures ALTER TABLE Learning_signatures
ADD COLUMN L1_misses BIGINT UNSIGNED AFTER perc_MPI, ADD COLUMN L1_misses BIGINT UNSIGNED AFTER perc_MPI,
...@@ -108,14 +96,9 @@ ADD COLUMN L2_misses BIGINT UNSIGNED AFTER L1_misses, ...@@ -108,14 +96,9 @@ ADD COLUMN L2_misses BIGINT UNSIGNED AFTER L1_misses,
ADD COLUMN L3_misses BIGINT UNSIGNED AFTER L2_misses; ADD COLUMN L3_misses BIGINT UNSIGNED AFTER L2_misses;
``` ```
### From EAR 4.1 to 4.2 ### From EAR 4.1 to 4.2
A field in the Events table had its name changed to be more generic. One can do that with EITHER of the following commands: A field in the Events table had its name changed to be more generic and its type changed to unsigned:
```
ALTER TABLE Events RENAME COLUMN freq TO value;
```
``` ```
ALTER TABLE Events CHANGE freq value INT unsigned; ALTER TABLE Events CHANGE freq value INT unsigned;
...@@ -178,8 +161,8 @@ EAR's database contains several tables, as described [here](#tables). Each table ...@@ -178,8 +161,8 @@ EAR's database contains several tables, as described [here](#tables). Each table
### Jobs ### Jobs
* <span dir="">id: Job id given by the scheduler (for example SLURM\_JOBID).</span> * <span dir="">id: Job id given by the scheduler (for example SLURM_JOBID).</span>
* <span dir="">step\_id: step id given by the scheduler.</span> * <span dir="">step_id: step id given by the scheduler.</span>
* user_id: the linux username that executed the job. * user_id: the linux username that executed the job.
* app_id: the application/job name as given by the scheduler (not necessarily the executable’s name) * app_id: the application/job name as given by the scheduler (not necessarily the executable’s name)
* start_time: timestamp of the job’s\[.step\] start * start_time: timestamp of the job’s\[.step\] start
...@@ -341,4 +324,4 @@ _This table is used by the EARGM._ ...@@ -341,4 +324,4 @@ _This table is used by the EARGM._
* start_time: timestamp of the start of the period * start_time: timestamp of the start of the period
* end_time: timestamp of the end of the period * end_time: timestamp of the end of the period
* DC_energy: accumulated energy consumed by the period * DC_energy: accumulated energy consumed by the period
* eardbd_host: hostname of the eardbd reporting the data to database. The hostnames of the nodes are trimmed at any “.”, i.e., service1.at.cluster becomes service1. * eardbd_host: hostname of the eardbd reporting the data to database. The hostnames of the nodes are trimmed at any “.”, i.e., service1.at.cluster becomes service1.
\ No newline at end of file
Clone repository
  • Home
  • User guide
    • Use cases
      • MPI applications
      • Non-MPI applications
      • Others
    • EAR data
    • Submission flags
    • Examples
    • Job accounting
    • Job energy optimization
  • 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
    • Architecture/Services
    • Quick installation guide
    • Installation from source
    • Installation from RPM
    • Updating
    • Configuration
    • Learning phase
    • Plug-ins
    • Supported systems
    • Powercap
  • Database
    • Updating the database from previous EAR versions
    • Tables description
  • CHANGELOG
  • FAQs
  • Known issues