Add running times to .json files

[oharboe]

Description

Based on my current best understanding, I would like to see the following added to the .json files:

• Add running time for .json file that the step corresponds to

Once running time is in the .json file, the make elapsed could be modified to use .json file information to reduce code duplication.

Suggested Solution

Add running time to .json file

Additional Context

No response

[oharboe]

@jeffng-or FYI

[maliberty]

Runtimes are fine to add (though I wouldn't set any metric limit on them).

Just because you have small skew/crpr on the worst path doesn't really tell you a lot. You might have terrible values on the second-worst path. What decision will you make based on these metrics?

[oharboe]

@maliberty Add running times for now and close this issue?

As you say, skew/CRPR is more of an in depth investigation than a simple metric issue.

[maliberty]

Add running times for now and close this issue?

Yes. Are you planning to make a PR or requesting PII do it?

[oharboe]

Add running times for now and close this issue?

Yes. Are you planning to make a PR or requesting PII do it?

It is a feature request to the community. It is not urgent. You asked why I'm not using the .json files in megaboom and I filed a few github issues w.r.t. issues with using the .json files.

[oharboe]

make elapsed could be rolled into .json if generation of .json files works SKIP_REPORT_METRICS=0

[harsh-kumar-patwa]

Hi, I'd like to work on this!

Currently genMetrics.py extracts elapsed times from log files but stores them as strings (e.g., "0:04.26") in the metrics JSON. This makes it hard to use them for analysis or plotting - consumers have to parse the time format manually.

I'll add numeric elapsed_seconds fields alongside the existing string fields in the generated metadata.json, so runtimes are directly usable as numbers. The existing string fields will be kept for backwards compatibility. I'll also add a numeric total_elapsed_seconds summing all stages.

[harsh-kumar-patwa]

Raised a PR for this : #3943

Added numeric elapsed_seconds fields alongside the existing string runtime__total fields in the metrics JSON. Each stage gets a <stage>__elapsed_seconds (float in seconds), and there's a total_elapsed_seconds for the sum. Existing fields are unchanged for backwards compatibility.

Let me know if anything needs adjusting!