Fixed MSLoss GPU utilization: completely rewritten for CUDA#33
Open
Fleyderer wants to merge 1 commit into
Open
Fixed MSLoss GPU utilization: completely rewritten for CUDA#33Fleyderer wants to merge 1 commit into
Fleyderer wants to merge 1 commit into
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When I've tried to train LMBN model using existing code, I've got a problem of very low GPU utilization: I could use 95% of GPU memory, but still had 7-10% of GPU utilization, while for half of a second I had 50% (absolutely typical situation when there are CPU - GPU usage problems).
After profiling I had this picture of trace:

First row of small magenta bars is CUDA usage. So you can see that when computing loss forward-backward, we spend like 2.5 seconds on CPU. After small research I've found that problem is in for-loops and min-max python functions, which are doing enormous count of CPU operations.
When I've fixed this code, I had 70-99% usage of GPU and 10x speed up of training (In my case it is 10 days -> 1 day).
Additionally, I will provide some code for input-output validation:
And then:
I've found that most of time these values are identical, while sometimes there is difference after
1e-7or1e-8which is an acceptable tolerance for GPU optimizations.