Add cancellation and resource monitoring to IMonitor (used for AutoML experiments) #6471
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.
Fixes #6320, #6465, #6426, #6425 and helps investigating further problems with AutoML trials.
This PR lets the user skip trials based various performance metrics. It changed my user experience with AutoML experiments significantly, because I regularly had crashes and failed trials when I tried to run experiments for a long time. With this modification I could implement my own IMonitor and react to changes in memory demand, disk space or I could skip a trial if it was running unexpectedly long.
Before the modifications my experiments usually stopped with an error in a few hours and after 15-20 trials, but now I just had my longest, 12-hour-long successful run with 729 trials!
I include my logs that were generated by my custom IMonitor implementation as an example: