Skip to content

Conversation

pbalcer
Copy link
Contributor

@pbalcer pbalcer commented Apr 8, 2025

No description provided.

@pbalcer pbalcer requested a review from a team as a code owner April 8, 2025 07:19
@pbalcer pbalcer temporarily deployed to WindowsCILock April 8, 2025 07:19 — with GitHub Actions Inactive
@pbalcer
Copy link
Contributor Author

pbalcer commented Apr 8, 2025

$ ZE_AFFINITY_MASK=0 taskset -c 5-20 ./main.py ~/workdir --sycl ~/llvm/build --ur ~/ur_install/ --adapter level_zero_v2 --iterations 1 --no-rebuild 
--filter "SubmitKernel in order"
Setting up ComputeBench
ComputeBench setup complete.
running api_overhead_benchmark_sycl SubmitKernel in order, iteration 0... 
api_overhead_benchmark_sycl SubmitKernel in order complete (api_overhead_benchmark_sycl SubmitKernel in order: 20.768 μs).
running api_overhead_benchmark_sycl SubmitKernel in order using eventless SYCL enqueue, iteration 0... 
api_overhead_benchmark_sycl SubmitKernel in order using eventless SYCL enqueue complete (api_overhead_benchmark_sycl SubmitKernel in order using eventless SYCL enqueue: 19.500 μs).
running api_overhead_benchmark_sycl SubmitKernel in order with measure completion, iteration 0... 
api_overhead_benchmark_sycl SubmitKernel in order with measure completion complete (api_overhead_benchmark_sycl SubmitKernel in order with measure completion: 24.616 μs).
running api_overhead_benchmark_sycl SubmitKernel in order with measure completion using eventless SYCL enqueue, iteration 0... 
api_overhead_benchmark_sycl SubmitKernel in order with measure completion using eventless SYCL enqueue complete (api_overhead_benchmark_sycl SubmitKernel in order with measure completion using eventless SYCL enqueue: 22.711 μs).
running api_overhead_benchmark_l0 SubmitKernel in order, iteration 0... 
api_overhead_benchmark_l0 SubmitKernel in order complete (api_overhead_benchmark_l0 SubmitKernel in order: 13.441 μs).
running api_overhead_benchmark_l0 SubmitKernel in order with measure completion, iteration 0... 
api_overhead_benchmark_l0 SubmitKernel in order with measure completion complete (api_overhead_benchmark_l0 SubmitKernel in order with measure completion: 18.243 μs).
running api_overhead_benchmark_ur SubmitKernel in order, iteration 0... 
api_overhead_benchmark_ur SubmitKernel in order complete (api_overhead_benchmark_ur SubmitKernel in order CPU count: 91950.000 instr).
api_overhead_benchmark_ur SubmitKernel in order complete (api_overhead_benchmark_ur SubmitKernel in order: 13.005 μs).
running api_overhead_benchmark_ur SubmitKernel in order with measure completion, iteration 0... 
api_overhead_benchmark_ur SubmitKernel in order with measure completion complete (api_overhead_benchmark_ur SubmitKernel in order with measure completion CPU count: 94024.000 instr).
api_overhead_benchmark_ur SubmitKernel in order with measure completion complete (api_overhead_benchmark_ur SubmitKernel in order with measure completion: 17.684 μs).

There's an appreciable improvement when using eventless enqueue.

@pbalcer pbalcer force-pushed the submitkernel-enqueue-func branch from 0cdb721 to a3c9cc9 Compare April 8, 2025 07:55
@pbalcer pbalcer temporarily deployed to WindowsCILock April 8, 2025 07:55 — with GitHub Actions Inactive
@pbalcer pbalcer temporarily deployed to WindowsCILock April 8, 2025 08:07 — with GitHub Actions Inactive
@pbalcer pbalcer temporarily deployed to WindowsCILock April 8, 2025 08:07 — with GitHub Actions Inactive
@pbalcer
Copy link
Contributor Author

pbalcer commented Apr 8, 2025

@intel/llvm-gatekeepers please merge

@dm-vodopyanov dm-vodopyanov merged commit 3469de7 into intel:sycl Apr 8, 2025
25 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.

4 participants