StormSurgeLive
Record resource usage to `run.properties` file
Resource usage monitoring and future use estimation will be enhanced by recording the SUs and storage used by each scenario. This information should be recorded as metadata in the run.properties file. This is separate from overall monitoring of an allocation (or storage) to determine total resources used/remaining.
@wwlwpd can you work on this? My initial thought is to add something to the queue script template that will record the cpu*hours that jobs actually use. We'd like to include single processor jobs for running adcprep. Also want to tally the total storage used by a scenario, although this will need to be in two phases: before and after archiving. The end result of these changes will be the addition of the following properties to the run.properties file:
hpc.job.partmesh.cpuhours : 0.5
hpc.job.prepall.cpuhours : 0.25
hpc.job.padcswan.cpuhours : 900.0
monitoring.resources.cpuhours : 900.75
monitoring.resources.storage.raw.mb : 10345.1
monitoring.resources.storage.archived.mb : 1981.9
The monitoring properties might all have to be computed and added to run.properties as a post processing step.
