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

The inconsistency between filtering by kernel and patch #382

Open
bangtianliu opened this issue Jul 15, 2024 · 1 comment
Open

The inconsistency between filtering by kernel and patch #382

bangtianliu opened this issue Jul 15, 2024 · 1 comment
Assignees
Labels
analysis Related to Omniperf's analyze mode bug Something isn't working

Comments

@bangtianliu
Copy link

Describe the bug
I use OmniPerf to profile the execution of Stable Diffusion XL (SDXL) on MI300X, where a single matmul_transpose_b kernel is executed 180 times. My focus is on the performance behavior of this matmul_transpose_b kernel. However, when I tried to filter by kernel and dispatch, I noticed some inconsistencies. Please check the below snapshots for the details, in which you can see the difference in the reported L2 cache hit rate.

Development Environment:

  • Linux Distribution: [Ubuntu 22.04.2 LTS]
  • Omniperf Version: [ 2.0.1 (release)]
  • GPU: [ MI300X]
  • Custer (if applicable): [e.g. Crusher, ]

To Reproduce
Steps to reproduce the behavior:
Maybe just found one application that will run the same kernel many times on GPUs, and then check the difference between filtering by dispatch and kernel

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
image
image

Additional context
Add any other context about the problem here.

@bangtianliu bangtianliu added the bug Something isn't working label Jul 15, 2024
@coleramos425
Copy link
Collaborator

coleramos425 commented Jul 15, 2024

Thanks @bangtianliu. For the record, I've tried reproducing this issue on an MI250 with the latest version of Omniperf (e.g. dev) and could not find the issue. The next step in this ticket would be to try reproducing on an MI300X.

Assigning the issue to project PM for triage.

@coleramos425 coleramos425 added the analysis Related to Omniperf's analyze mode label Jul 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
analysis Related to Omniperf's analyze mode bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants