-
Notifications
You must be signed in to change notification settings - Fork 49
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
[AutoTuner] Add first verison of autotuner #124
Merged
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
Caozhou1995
force-pushed
the
base_autotuner
branch
6 times, most recently
from
May 27, 2024 11:03
69abfe8
to
1e7a558
Compare
Caozhou1995
force-pushed
the
base_autotuner
branch
2 times, most recently
from
May 28, 2024 10:03
373175b
to
6a2c26f
Compare
Caozhou1995
force-pushed
the
base_autotuner
branch
from
May 28, 2024 10:51
6a2c26f
to
da75397
Compare
Caozhou1995
force-pushed
the
base_autotuner
branch
from
May 30, 2024 11:33
fe0fb2d
to
f98388a
Compare
Caozhou1995
force-pushed
the
base_autotuner
branch
2 times, most recently
from
May 30, 2024 12:25
b318cad
to
47d89ec
Compare
Caozhou1995
force-pushed
the
base_autotuner
branch
from
May 30, 2024 12:26
47d89ec
to
ad10e26
Compare
Caozhou1995
force-pushed
the
base_autotuner
branch
from
May 31, 2024 04:20
d27d136
to
245e6c1
Compare
Closed
Caozhou1995
force-pushed
the
base_autotuner
branch
from
June 4, 2024 07:16
95b63f0
to
c392027
Compare
Caozhou1995
force-pushed
the
base_autotuner
branch
from
June 4, 2024 07:18
c392027
to
32b3e67
Compare
Caozhou1995
force-pushed
the
base_autotuner
branch
4 times, most recently
from
June 5, 2024 06:09
8484221
to
4e7b289
Compare
Caozhou1995
force-pushed
the
base_autotuner
branch
from
June 5, 2024 06:12
4e7b289
to
0fb14a3
Compare
Caozhou1995
force-pushed
the
base_autotuner
branch
from
June 5, 2024 08:56
2eb7074
to
53e9dcc
Compare
phoenixdong
previously approved these changes
Jun 5, 2024
Caozhou1995
force-pushed
the
base_autotuner
branch
2 times, most recently
from
June 6, 2024 02:48
5778d21
to
08efd6e
Compare
Caozhou1995
force-pushed
the
base_autotuner
branch
from
June 6, 2024 03:31
08efd6e
to
d9af983
Compare
Caozhou1995
force-pushed
the
base_autotuner
branch
from
June 6, 2024 08:48
c1f9e1e
to
e5e9c7d
Compare
aoyulong
approved these changes
Jun 6, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
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 adds autotuner module, which can be used with one click by setting
action=auto_tune
, just like:python run.py --config-path ./examples/aquila/conf --config-name config action=auto_tune
.AutoTuner currently supports the search of all major parallel strategies, including:
AutoTuner is user-friendly, users can add auto_tuner fields on the basis of training yaml to custom, such as follows:
Currently we implement a heuristic grid search algorithm with built-in efficient pruning strategies based on historical results, and more search algorithms will be added in the future, so users don't need to care about these parts at present.
Where
space
is the search space, the user can customize the candidate value of each dimension, if not defined, there will be a default value by framework. We have the following search dimensions built in:control
is used to control the search process, such as the maximum running time of each task, how many steps are run, the maximum running time of autotuner, etcWhen the auto tuner running, each task has a corresponding log directory, and the results are summarized and sorted that users only need to look at the csv to know the detailed data for task.