-
Notifications
You must be signed in to change notification settings - Fork 167
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[RFC] hivemind.Optimizer overhaul #400
Closed
Closed
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
Codecov Report
@@ Coverage Diff @@
## master #400 +/- ##
==========================================
+ Coverage 84.09% 84.19% +0.10%
==========================================
Files 77 77
Lines 7891 7891
==========================================
+ Hits 6636 6644 +8
+ Misses 1255 1247 -8
|
So far, all discussion we've had on this was oral. So, lemme summarize what we've agreed on with @mryab @borzunov @yhn112 :
... and then we'll figure out the rest of the features |
This was referenced Nov 6, 2021
justheuristic
added a commit
that referenced
this pull request
Nov 8, 2021
This PR implements GradientAverager - a subclass of DecentralizedAverager that supports accumulating and aggregating gradients. This class supports pre-scheduling and delayed averaging ( for DPU, #394 ) for use in hivemind.Optimizer ( #400 ) Co-authored-by: Max Ryabinin <[email protected]> Co-authored-by: Aleksandr Borzunov <[email protected]>
6 tasks
justheuristic
added a commit
that referenced
this pull request
Nov 15, 2021
This PR implements a component of hivemind.Optimizer ( #400 ) that holds the training state and supports (delayed) optimizer steps and averaging rounds. Unlike TrainingAverager, this class is does not need data locks as it will only update model parameters during .step. Co-authored-by: Roman Zhytar <[email protected]> Co-authored-by: Anton Sinitsin <[email protected]> Co-authored-by: Max Ryabinin <[email protected]> Co-authored-by: Aleksandr Borzunov <[email protected]>
Status report:
|
12 tasks
Most of this implemented in several PRs towards the 1.0.0 release. |
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.
Current experience with hivemind optimizers
Where it hurts:
What worked:
Additional constraints:
Proposal: interface
Replace the 4 existing optimizers with a single one
The new optimizer would cover all 5 existing ones as special cases:
Optimizer(opt=SGD(...), average_parameters=True)
Optimizer(opt=Adam(...), average_parameters=True, average_statistics=("exp_avg_sq",))
Optimizer(opt=..., average_gradients=True, target_batch_size=4096, average_parameters=True)
Optimizer(opt=..., average_gradients=True, target_batch_size=4096, average_parameters=True, average_statistics=("exp_avg_sq",))
Optimizer(..., average_gradients=True, async_gradient_averaging=True, **same_as_above)
Proposal: internals
TODOs
create hivemind.Optimizer
basic features
#samples
)advanced features
update tutorials
refactoring / chores