Add random delay during multiple job launch to break tie #1243
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.
Signed-off-by: Isaac Yang isaacy@nvidia.com
Fixes #1236 .
Description
GPU idle detection may have a race condition if multiple jobs are launched at nearly the same time. Add some random delay to break the tie.
The logs from four jobs in reported failed pipeline showed all of them were assigned to GPU 0 and 3. That meant all of them reached the detection code at the same time and at the time, none of them was using GPU.
The number 16 can be larger so the probability of two jobs being launched side-by-side is reduced.
The number 60 is to give time for unittest code to start allocating GPU memory, and for other instance to be aware of GPU utilization by others.
Status
Ready
Types of changes
./runtests.sh --codeformat --coverage../runtests.sh --quick.make htmlcommand in thedocs/folder.