Removing .float()
(autocast
in fp16 will discard this (I think)).
#495
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.
While investigating performance improvements, the main culprit I found was
autocast
which actually adds a LOT of copies of tensors a bit everywhereto cast to
float16
. I added a lot of custom made casts for now in an offbranch.This PR tries to check 1 of the changes which is this
.float()
cast which breakin
fp16
mode (because the model is in fp16, while the tensor is now infloat
.