Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
P
predtuner
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
llvm
predtuner
Commits
0224731f
Commit
0224731f
authored
4 years ago
by
Yifan Zhao
Browse files
Options
Downloads
Patches
Plain Diff
Use 'kept' configs consistently throughout
parent
9261e5ec
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/getting_started.rst
+11
-9
11 additions, 9 deletions
doc/getting_started.rst
with
11 additions
and
9 deletions
doc/getting_started.rst
+
11
−
9
View file @
0224731f
...
...
@@ -125,15 +125,17 @@ We will be using the term QoS throughout the tutorials.
:py:meth:`tuner.tune <predtuner.modeledapp.ApproxModeledTuner.tune>`
is the main method for running a tuning session.
It accepts a few parameters which controls the behavior of tuning.
`max_iter` defines the number of iterations to use in autotuning.
Within 1000 iterations, PredTuner should find about 200 valid configurations.
PredTuner will also automatically mark out `Pareto-optimal
<https://en.wikipedia.org/wiki/Pareto_efficiency>`_
configurations.
These are called "best" configurations (`tuner.best_configs`),
in contrast to "valid" configurations which are the configurations that satisfy our accuracy requirements
(`tuner.kept_configs`).
`take_best_n` allows taking some extra close-optimal configurations in addition to Pareto-optimal ones.
* `qos_keep_threshold` decides the QoS threshold above which the found configuration is kept.
These are called the "kept" configurations and are accessible from `tuner.kept_configs`.
* `max_iter` defines the number of iterations to use in autotuning.
Within 1000 iterations, PredTuner should be about to find about 200 "kept" configurations.
* PredTuner will also automatically mark out
`Pareto-optimal <https://en.wikipedia.org/wiki/Pareto_efficiency>`_ configurations.
These are called "best" configurations (`tuner.best_configs`)
`take_best_n` allows taking some extra close-optimal configurations in addition to Pareto-optimal ones.
1000 iterations is for demonstration; in practice,
at least 10000 iterations are necessary on VGG16-sized models to converge to a set of good configurations.
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment