[SIGGRAPH 2020] Fixing cuBLAS issue under Windows #65
Conversation
This file contains 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.
Training could not be reproduced out of the box under a Windows system. Python environment would point a problem initializing cuBLAS (and all further operations requiring it).
Borrowed a fix described at https://stackoverflow.com/a/52132342 and training was possible as expected.
Do note: I'm not not a TF expert myself, so I can't know if said inclusion would affect overall compatibility.
Similar issues all relate to memory growth. More recent documentation point to alternative solutions as in https://stackoverflow.com/a/60699372
Thanks for the generosity with the code!