Skip to content

[XPTI][INFRA] Fixes minor standalone build and code issues #18452

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

Open
wants to merge 3 commits into
base: sycl
Choose a base branch
from

Conversation

tovinkere
Copy link
Contributor

This PR is first of many XPTI changes to address the performance issues that have been reported.

(1) xpti::Framework::instance() - testing the use of std::call_once against current implementation
(2) Added cleanup for default stream "xpti.framework"
(3) Switched to EmHash instead of std::unordered_map that improve notification performance by 10%

Most of the performance overheads are from xptiRegisterObject() and xptiAddMetadata(). This requires changes in the SYCL runtime an will be addressed in a subsequent PR

tovinkere added 2 commits May 13, 2025 08:18
 - Tested std::call_once against current implementation
   in Framework::instance() and saw no increase in
   performance overhead
 - Added cleanup for default stream "xpti.framework"

Signed-off-by: Vasanth Tovinkere <[email protected]>
 - Switched to EmHash for notifications and this improves
   performance by 10%

Signed-off-by: Vasanth Tovinkere <[email protected]>
@tovinkere tovinkere requested a review from a team as a code owner May 13, 2025 20:20
@tovinkere tovinkere requested a review from steffenlarsen May 13, 2025 20:20
Copy link
Contributor

@steffenlarsen steffenlarsen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, but I would like to hear @KseniyaTikhomirova's thoughts as well.

Copy link
Contributor

@KseniyaTikhomirova KseniyaTikhomirova left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@@ -1,6 +1,6 @@
cmake_minimum_required(VERSION 3.20.0)
cmake_minimum_required(VERSION 3.5)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why is it 3.5? is it intentional change?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was testing with CMake 4.0 and that was the minimum requirement - reverted back to 3.20.0

@tovinkere
Copy link
Contributor Author

Failure is unrelated with an open issue already.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants