WIP: Keep results on CPU to avoid OOM #148
Open
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.
To fix issues with OOM with large audio files, I made some changes so that the large tensors are on the CPU and not on the GPU.
This implementation of course introduces a slight amount of overhead because of CPU-GPU transfer. It should'nt be too much though.
Please let me know what you think. If you agree with this approach, it could be extended to the other model architectures too.
Fixes #120, #109 and other similar OOM issues.