-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Fix ray hyperopt #1999
Fix ray hyperopt #1999
Conversation
res = ray.init( | ||
num_cpus=4, | ||
num_cpus=10, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think GH runners have 10 cpus. Do we really need this many? I think if it can't run with like 6 at most, there's probably a bug somewhere.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@tgaddair we would need at least one more CPU than the CPUs used in hyperopt trials (discussed in this slack thread).
We could artificially restrict hyperopt to run less than 6 trials so that there are CPUs available for dask computation by setting max_concurrent_trials
to something less than 6. For now, I've changed the number of CPUs to 7.
c69ac82
to
002eb35
Compare
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
…actor, added a df_engine attribute to RayPredictor
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, only one small thing.
for more information, see https://pre-commit.ci
No description provided.