Skip to content
GitLab

EAR Database · Changes

Page history
EAR Wiki - 4.3.1 authored by Oriol Vidal Teruel's avatar Oriol Vidal Teruel
Hide whitespace changes
Inline Side-by-side
EAR-Database.md
View page @ 262727c8
......@@ -76,6 +76,24 @@ Additionally, if EAR was compiled in a system with GPUs (or with the GPU flag ma
## Updating from previous versions
### From EAR 4.3 to 4.4
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;
```
### From EAR 4.2 to 4.3
Three new fields corresponding to L1, L2 and L3 cache misses have been added to the signatures.
......@@ -190,12 +208,13 @@ EAR's database contains several tables, as described [here](#tables). Each table
_All the metrics in this table refer to the period of time where the Signature is computed. Typically is 10 sec. Signatures are only reported when the application uses the EAR library._
* id: unique id generated by the database engine to be used in JOIN queries.
* DC_power: average DC node power (in Watts)
* DRAM_power: average DRAM power, including the 2 sockets (in Watts)
* PCK_power: Average CPU power, including the 2 sockets (in Watts)
* EDP: Energy Delay Product computed as (time x time x DC_power)
* GBS: Main memory bandwidth (GB/sec)
* TPI: Main memory transactions per instruction
* DC_power: average DC node power (in Watts).
* DRAM_power: average DRAM power, including the 2 sockets (in Watts).
* PCK_power: Average CPU power, including the 2 sockets (in Watts).
* EDP: Energy Delay Product computed as (time x time x DC_power).
* GBS: Main memory bandwidth (GB/sec).
* IO_MBS: I/O read and write rate (MB/s).
* TPI: Main memory transactions per instruction.
* CPI: Cycles per instructions.
* Gflops: Giga Floating point operations, per second, generated by the application processes in the node. GFlops/sec.
* time: total execution time (in seconds)
......@@ -211,13 +230,13 @@ _All the metrics in this table refer to the period of time where the Signature i
* FLOPS6: Floating point operations Double precision 128 bits consumed by application processes in the node.
* FLOPS7: Floating point operations Double precision 256 bits consumed by application processes in the node.
* FLOPS8: Floating point operations Double precision 512 bits consumed by application processes in the node.
* instructions: total instructions executed by the application processes in the node
* cycles: total cycles consumed by the application processes in the node
* avg_f: average CPU frequency (includes all the cores used by the application on the node) in KHz
* avg_imc_f: average memory frequency (includes the two sockets) in KHz
* def_f: default CPU frequency used at the beginning of the application in KHz
* min_GPU_sig_id: start of the range containing the GPU_signature’s ids, used for JOIN queries. If an application doesn’t have GPUs it will be NULL
* max_GPU_sig_id: end of the range containing the GPU_signature’s ids, used for JOIN queries. If an application doesn’t have GPUs it will be NULL
* instructions: total instructions executed by the application processes in the node.
* cycles: total cycles consumed by the application processes in the node.
* avg_f: average CPU frequency (includes all the cores used by the application on the node) in KHz.
* avg_imc_f: average memory frequency (includes the two sockets) in KHz.
* def_f: default CPU frequency used at the beginning of the application in KHz.
* min_GPU_sig_id: start of the range containing the GPU_signature’s ids, used for JOIN queries. If an application doesn’t have GPUs it will be NULL.
* max_GPU_sig_id: end of the range containing the GPU_signature’s ids, used for JOIN queries. If an application doesn’t have GPUs it will be NULL.
> 1. Each signature corresponds to either a Loop or an Application. When it’s an application it is the average values for its entire runtime. For a loop, the values are the average of only the period comprised by the loop’s start and end.
> 2. Signatures are only reported when an application is running with EARL.
......