This repository was archived by the owner on Mar 28, 2023. It is now read-only.
[ESIMD] Fix sporadic timeouts of matrix_transpose test #391
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
|
@DenisBakhvalov could you please add some description for the fix? |
Done |
vladimirlaz
approved these changes
Aug 9, 2021
aelovikov-intel
pushed a commit
to aelovikov-intel/llvm
that referenced
this pull request
Mar 27, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ESIMD
matrix_transpose.cpptest sporadically hanged when running simultaneously in 2 threads. I observed 7 timeouts out of 1000 total (500 for each thread) runs.We have a similar ESIMD
matrix_transpose_usm.cpptest, which is the same test but uses USM pointers instead of accessors. The only difference is in the working set, which seems to be the reason for this strange behavior. With the current patch, I got 0 timeouts for 1000 total runs.The reason for the original hang is further investigated on the backend side.