This repository has been archived by the owner on Nov 17, 2023. It is now read-only.
2bit gradient compression #8728
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
eric-haibin-lin
pushed a commit
to eric-haibin-lin/mxnet
that referenced
this pull request
Dec 3, 2017
* 2bit gradient compression * trigger CI
zhreshold
pushed a commit
to zhreshold/mxnet
that referenced
this pull request
Dec 14, 2017
* 2bit gradient compression * trigger CI
|
@rahul003 Very happy to see the gradient compression has been merged! Can the 2bit compression support the sparse compression now? |
rahul003
added a commit
to rahul003/mxnet
that referenced
this pull request
Jun 4, 2018
* 2bit gradient compression * trigger CI
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Resending PR as my old PR was merged, then reverted because there were concerns that it was prematurely merged. Do you think this can be merged now?
@piiswrong @eric-haibin-lin
Please see PR #8662 for all details and results