CPU-only baby steps#136
Merged
jeffra merged 9 commits intoMar 13, 2020
Merged
Conversation
* allow installing a specific apex commit
* add support for torch 1.3+ builds inside a docker build environment * remove apex imports
…, torch doesn't support fp16 on cpu :(
This file contains hidden or 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
2 participants
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 does a few things:
deepspeed/git_version_info.pytodeepspeed/install_config.py. We now storepython_onlythere.deepspeed.__cpu_only__anddeepspeed.__python_only__. I split up CPU and Python options here in order to minimize feature loss (i.e., Python-only on a GPU shouldn't necessarily lose FP16?). I figure we should add--cpu-onlytoinstall.shtoo? Having the two options will be confusing though. Not sure of the best way to interface.