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

[Profiler] Enable Triton Proton for the Intel GPU's #1145

Open
chengjunlu opened this issue May 17, 2024 · 0 comments · May be fixed by #2635
Open

[Profiler] Enable Triton Proton for the Intel GPU's #1145

chengjunlu opened this issue May 17, 2024 · 0 comments · May be fixed by #2635
Assignees
Labels
enhancement New feature or request performance

Comments

@chengjunlu
Copy link
Contributor

Related to the issue #1066.

We uses the the SYCL barrier to measure the Triton kernel performance which is not accurate especially after the immediate command list function is enabled.

The Triton XPU micro-benchmark now switch to use the SYCL event and IPEX profiler extension to measure the performance. But the IPEX profiler extension is going to be removed.

We need to formally support the Triton Proton profiler tools.

@vlad-penkin vlad-penkin added enhancement New feature or request performance labels May 20, 2024
@vlad-penkin vlad-penkin added this to the 4.0 [Performance] Core milestone May 20, 2024
@anmyachev anmyachev self-assigned this Oct 24, 2024
@anmyachev anmyachev linked a pull request Nov 5, 2024 that will close this issue
4 tasks
@vlad-penkin vlad-penkin changed the title [Profiler] To support Triton profiler Proton to profile the Intel GPU kernel performance [Profiler] Enable Triton Proton profiler for the Intel GPU's Nov 12, 2024
@vlad-penkin vlad-penkin changed the title [Profiler] Enable Triton Proton profiler for the Intel GPU's [Profiler] Enable Triton Proton for the Intel GPU's Nov 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request performance
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants