TensorFlow: fix word2vec timeouts on GPU by pinning model on CPU #1007
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
CPU. Right now word2vec is not well supported on GPU (missing scatter sub, etc). We can remove this limitation later when ScatterSub and other ops are all available on GPU.
|
LGTM. The test failures you see on the PR gpu-pip build is due to a separate known issue. |
martinwicke
added a commit
that referenced
this pull request
Feb 7, 2016
|
merged. |
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.
Right now word2vec is not well supported on GPU (missing
scatter sub, etc). We can remove this limitation later when
ScatterSub and other ops are all available on GPU.
With this fix, the two word2vec tests now run in 5 seconds on a machine with GPU.