-
Notifications
You must be signed in to change notification settings - Fork 219
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
xpu.Event reporting erroneous times #568
Comments
Hi @garrett361, I will try to reproduce the issue and get back to you. |
Hi @hueyline have you been able to reproduce this? |
Hi @garrett361 , thank you for reporting this, I can reproduce the inconsistency and I have report it to dev team and they will fix it! |
WIP... |
Hi @garrett361 , |
Hi @ZhaoqiongZ, thank you for the response. The example above uses
All of my use cases are
I would like to understand the root cause better. Could you please expand upon the issue? I would like to know what types of issues are affected in general. Thank you! |
Hi @garrett361 , for original case, it works only in 2.1.30+xpu with the proper driver 803, and for the version you use, it seems before 21.30 and previous driver, it will output the random wrong time. |
Describe the bug
Hi, I am trying to time
xpu
operations usingxpu.Event
analogously to howcuda.Event
is used and getting unexpected results. Isxpu.Event
supported? I didn't see this behavior reported elsewhere.The following script times multiple one-second chunks and prints out the results:
On CUDA this works fine:
But on
xpu
:The specific results on
xpu
also vary widely. Running the same script a few more times converges to outputs which more typically look like:Versions
Results of
collect_env.py
:aand some
xpu-smi discovery
printout:The text was updated successfully, but these errors were encountered: