User Tools

Site Tools


energy_taskforce

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
energy_taskforce [2017/07/28 12:13]
neil
energy_taskforce [2017/09/29 15:30] (current)
Line 17: Line 17:
  
 Breaking down the application requirements (expressed in XMML) it is possible to classify each application as a series of common types. This enables associated dummy jobs to be created for each type. These can be run periodically to generate energy tags that reflect the current state of HPC resource. Breaking down the application requirements (expressed in XMML) it is possible to classify each application as a series of common types. This enables associated dummy jobs to be created for each type. These can be run periodically to generate energy tags that reflect the current state of HPC resource.
 +
 This periodic running of the test jobs can save energy and time by reducing the amount of jobs to be run to get energy tags from per application to a sample size for example of per 100 applications. Actual run time and energy data from completed jobs will be used to weight the predicted performance by the test jobs enabling a view on scheduler accuracy. This periodic running of the test jobs can save energy and time by reducing the amount of jobs to be run to get energy tags from per application to a sample size for example of per 100 applications. Actual run time and energy data from completed jobs will be used to weight the predicted performance by the test jobs enabling a view on scheduler accuracy.
 +
 +{{:​eas.png?​400|}}
  
 Application Application
Line 38: Line 41:
  
 Actions Actions
 +
 1. Upload the outline document to the wiki (NM). 1. Upload the outline document to the wiki (NM).
  
energy_taskforce.txt ยท Last modified: 2017/09/29 15:30 (external edit)