ES-DOC / esdoc-cim-v2-schema

Canonical CIM schema v2 definition
2 stars 5 forks source link

Consider ENES HPC TF metrics: should these be included in performance? #13

Closed bnlawrence closed 4 years ago

bnlawrence commented 5 years ago

Might be an optional set of questions ... or a profile, or what. Anyway, these are they:

Metric Description
Model Model name and version
CMIP6 Config Descriptive tag of CMIP6 experiment
Platform Machine used
Total Simulated Years Total number of years simulated for the CMIP6 experiment
Data Produced Size Total data outputs produced by the CMIP6 experiment (Total disk space required for all data saved from CMIP6 runs)
Total core hours Total number of core hours used by the CMIP6 experiment
Pflops-hour peak and linpack Equivalent Peak and Linpack PFlop-hours. For a given computer used look up the total number of cores (N), the total peak performance (RPeak) and the Linpack Performance (Rmax) in the Top 500 list (http://www.top500.org/list). Equivalent Peak and Linpack performance are then given by CRpeak/N and CRmax/N respectively where C is the number of core hours given (total core hours) by the experiment.
bnlawrence commented 5 years ago

Clearly some of them need to discriminate between the number recorded in the CMIP6 archive, and the number carried out. However, these are really not performance metrics, but rather experiment "support metrics". Need to think about how best to handle those.

davidhassell commented 5 years ago

As you have said (partially or wholly) elsewhere, Bryan ...

Pflops-hour, peak and linpack could be added to compute_pool (https://github.com/ES-DOC/esdoc-cim-v2-schema/blob/master/platform_classes.py#L39).

Model, CMIP6 config, platform are already in the CIM.

I'm not sure what to do about the others to do with aggregated amounts across all simulations in an experiment. Perhaps the Ensemble (https://github.com/ES-DOC/esdoc-cim-v2-schema/blob/master/activity_classes.py#L119) could have some "resources" properties added to it to capture them?

If we can get all of these into the CIM, compiling this entire table from the ES-DOC will be trivial.

bnlawrence commented 4 years ago

I've added a new class in platform: ``project_cost'' which addresses some of these things, but not the linkpack, pflop stuff ... which belongs in machine. It's yuck. I'll add it there.