Skip to content
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

Build SMI-sampling to get more accurate clock rates #174

Open
coleramos425 opened this issue Aug 25, 2023 · 0 comments
Open

Build SMI-sampling to get more accurate clock rates #174

coleramos425 opened this issue Aug 25, 2023 · 0 comments
Labels
Omniperf Revamp Ticket related to the redesign of Omniperf
Milestone

Comments

@coleramos425
Copy link
Collaborator

Describe the suggestion
Build SMI-sampling to get more accurate clock rates

Justification
see here: #149 (comment). Basically, we'd ideally want a good average of clock rates from the profiler for each kernel. Note that 'other' profilers give the ability to either control the clock rate (subject to throttling) or actively report the number of clocks elapsed in various time domains.

Implementation
It can be as simple as spinning up a background thread to sample the clock rate during the app, but a more robust version would be able to assign clocks to specific kernels (e.g., if we control rocprofiler directly as well). We might also ask for enhanced rocprofiler support.

Additional Notes
We might also be able to do this by using (EndNs - BeginNs) / GRBM_GUI_ACTIVE to get an approximate clock rate?

Originally posted by @arghdos in #153 (comment)

@coleramos425 coleramos425 added the Omniperf Revamp Ticket related to the redesign of Omniperf label Aug 25, 2023
@coleramos425 coleramos425 added this to the v1.2.0 milestone Aug 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Omniperf Revamp Ticket related to the redesign of Omniperf
Projects
None yet
Development

No branches or pull requests

1 participant