Do not persist entire AutoMLState in Searcher #870
Merged
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.
Signed-off-by: Antoni Baum antoni.baum@protonmail.com
Why are these changes needed?
Currently, the entire
AutoMLState
is persisted in Searcher as a part of theconfig_constraints
. As the State object contains the dataframe used, this means a large amount of data will be persisted to disk as a part of automatic Tune Experiment checkpointing, leading to large disk usage and high performance overhead, causing various bottlenecks.This PR changes the
size
function used inconfig_constraints
to only consider thelearner_classes
attribute ofAutoMLState
which removes the issue of too much data being saved.Related issue number
Closes #866
Checks