Skip to content

[benchmarks][BMG] The profiling numbers don't match #4172

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

Closed
Egor-Krivov opened this issue May 12, 2025 · 5 comments · Fixed by #4244
Closed

[benchmarks][BMG] The profiling numbers don't match #4172

Egor-Krivov opened this issue May 12, 2025 · 5 comments · Fixed by #4244

Comments

@Egor-Krivov
Copy link
Contributor

There was clearly some change in benchmarking method during the last 4 days.

BMG benchmarks first worked https://github.com/intel/intel-xpu-backend-for-triton/actions/runs/14905112564/job/41865599494

Then there was an issue with benchmarking method
https://github.com/intel/intel-xpu-backend-for-triton/actions/runs/14944793130/job/41986732315

Now there is an issue with profiling numbers
https://github.com/intel/intel-xpu-backend-for-triton/actions/runs/14947685095/job/41993124069

Clearly something changed. Likely culprit:
dc14d64

@anmyachev
Copy link
Contributor

@kwasd @pbchekin At first I thought that DLE had already been updated for BMG, but considering #4173 issue, I'm not sure anymore. Could you clarify?

@pbchekin
Copy link
Contributor

@kwasd @pbchekin At first I thought that DLE had already been updated for BMG, but considering #4173 issue, I'm not sure anymore. Could you clarify?

A770, BMG, and LNL runners have been updated. Others to follow, we will report our progress shortly.

@pbchekin
Copy link
Contributor

I think this issue started with upgrading to DLE 2025.1.1, actually.

@anmyachev
Copy link
Contributor

Most likely we need pti 0.12.1 to make it work correctly.

@anmyachev
Copy link
Contributor

https://pypi.org/project/intel-pti/0.12.1 release was yanked. Waiting for 0.12.2

@anmyachev anmyachev linked a pull request May 20, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants