Disallow PythonLayer in Multi-GPU training #3032
Merged
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
ronghanghu
force-pushed
the
ban-pythonlayer-in-parallel
branch
from
a559518
to
1394cdc
Compare
shelhamer
added a commit
that referenced
this pull request
Sep 25, 2015
Disallow PythonLayer in Multi-GPU training
|
This is meant to be a partial workaround before we have better solutions. #2939 seems better than this PR (to me) but needs more testing. |
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.
This PR disallow PythonLayer during Multi-GPU training phase. Otherwise it crash due to GIL issues #2936.
@jeffdonahue @longjon @shelhamer We should merge either this PR or #2939, to fix PythonLayer crash in Multi-GPU.