-
Notifications
You must be signed in to change notification settings - Fork 64
Improve baseline comparison logic #817
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: develop
Are you sure you want to change the base?
Conversation
6b94a8f
to
d061c1c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Please separate gfx906 deprecation out of this pr.
- Keep block IDs is important. When we are talking about "baseline comparison", the 1st run is used as baseline reference, which implies all the info from the 1st run are the baseline including block IDs.
And just for internal maintain/design purpose, we have meta info in the comments(temporally) for the reasons why we don't have the metrics available. It is better to provide solution when removing those. |
My concern is, does it make sense to compare a metric when its only available in one run?
OK
We can backport the metrics from MI350 config to older GPUs when someone ask for it in a different PR. |
This will be tracked in #819 |
* Do not force unsupported metrics to be specified in older gpu architectures as None * Remove metrics which are explicitly set to None * Update CHANGELOG * Fix analysis configuration to fix baseline comparisons across all gpu architectures * Add missing 1812 section for gfx908 * Add missing 1812 section for gfx90a
d061c1c
to
60b2879
Compare
There is no such thing as block IDs, I think you are referring to Metric ID and i dont think that adds any value to the analysis report. Metric ID will still be shown in non baseline comparison mode. Only in baseline comparison mode its not able to show Metric ID due to metrics being different. |
As discussed on call, we can add Metric ID from first workload during baseline comparison. |
rocprofiler-compute Pull Request
Related Issue
What type of PR is this? (check all that apply)
Technical Details
Do not force unsupported metrics to be specified in older gpu
architectures as None
Remove metrics which are explicitly set to None
Update CHANGELOG
Fix analysis configuration to fix baseline comparisons across all gpu
architectures
We cannot guarantee common Metric ID index for metrics comparison across different GPU models.
The Metric ID is not very useful anyways and this is how it looks with and without Metric ID
With Metric ID
Without Metric ID

Have you added or updated tests to validate functionality?
Validated baseline comparison working across all gpu architectures
Added / Updated documentation?
Have you updated CHANGELOG?