-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Better per_run_time_limit default #764
Comments
@mfeurer Should this take on account the number of jobs? So |
|
Hello! As of now, 2 arguments control the time limit enforcing, and both of them are agnostic to the number of jobs.
So if n_jobs>1, autosklearn code creates several automl objects that each one of them call smac with time_left_for_this_task/per_run_time_limit directly as provided to the user. So shouldn't this per_run_time_limit be 1/10 of time_left_for_this_task instead of 1/10 of n_jobs * time_left_for_this_task ? Else, we should clarify also about what is the implication to the other argument time_left_for_this_task. |
Actually, I would suggest making In my opinion, the |
Closing this as we merged this via #884. |
Currently, the hyperparameter
per_run_time_limit
is set to 360s. However it should be 1/10 of the total time limit per default.The text was updated successfully, but these errors were encountered: