Skip to content

[SYCL] Change the kernel and program cache data structures to std #17295

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

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

Conversation

slawekptak
Copy link
Contributor

The goal of this change is to limit the dependencies.

@slawekptak slawekptak requested a review from a team as a code owner March 4, 2025 14:44
@slawekptak slawekptak requested a review from cperkinsintel March 4, 2025 14:44
@uditagarwal97
Copy link
Contributor

The goal of this change is to limit the dependencies.

What's the performance implication of this change?

@slawekptak
Copy link
Contributor Author

The goal of this change is to limit the dependencies.

What's the performance implication of this change?

In my tests, I haven't seen any performance drop up to 1k distinct kernels (distinct kernels being separate lambdas or a distinct value of a specialization constant). With 10k kernels I've seen a small drop (few percent).

@uditagarwal97
Copy link
Contributor

. With 10k kernels I've seen a small drop (few percent).

Applications with > 10K kernels are not uncommon - ML applications are huge and can easily invoke thousands of kernels and a few percent perf. drop can become significant in that case.

The goal is to use the std data structure for the kernel
fast cache.
The goal is to use the std data structures for the kernel
caches.
The goal is to use the std data structure for the program
cache.
@slawekptak slawekptak marked this pull request as draft March 7, 2025 15:23
@slawekptak slawekptak changed the title Change the kernel and program cache data structures to std [SYCL] Change the kernel and program cache data structures to std Mar 7, 2025
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.

2 participants