[ML] Account for data frame memory in the peak memory usage estimate for classification and regression #996
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.
We weren't accounting for the data frame's memory usage when reporting peak memory usage for training. Also, we were missing some state when estimating peak memory usage during the line searches to initialise hyperparameters.
I've also taken the opportunity to more fully migrate instrumentation of training to use the new instrumentation object and provide better automatic stubbing.