Skip to content

[SYCL] use vector instead of map as a kernel cache container #18833

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

Merged
merged 1 commit into from
Jun 6, 2025

Conversation

vinser52
Copy link
Contributor

@vinser52 vinser52 commented Jun 5, 2025

We assume that in most cases, there is only a single context/device per kernel. Considering that using a vector instead of the hash map performs better on a common case scenarios.

@vinser52 vinser52 requested a review from a team as a code owner June 5, 2025 16:10
@vinser52 vinser52 requested a review from againull June 5, 2025 16:10
@vinser52 vinser52 requested a review from sergey-semenov June 5, 2025 22:50
@vinser52 vinser52 force-pushed the kernel_cache_container branch from 2a83283 to 2f89156 Compare June 5, 2025 22:51
@vinser52 vinser52 temporarily deployed to WindowsCILock June 5, 2025 22:51 — with GitHub Actions Inactive
@vinser52 vinser52 temporarily deployed to WindowsCILock June 6, 2025 00:01 — with GitHub Actions Inactive
@vinser52 vinser52 temporarily deployed to WindowsCILock June 6, 2025 00:01 — with GitHub Actions Inactive
@againull againull merged commit 43b3d42 into intel:sycl Jun 6, 2025
24 checks passed
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