-
Notifications
You must be signed in to change notification settings - Fork 554
[MRG] added n_jobs support to optimizer #627
Conversation
|
Hello @jonathanng! Thanks for updating the PR. Cheers ! There are no PEP8 issues in this Pull Request. 🍻 Comment last updated on February 01, 2018 at 17:38 Hours UTC |
Codecov Report
@@ Coverage Diff @@
## master #627 +/- ##
==========================================
+ Coverage 86.6% 86.61% +<.01%
==========================================
Files 23 23
Lines 1777 1778 +1
==========================================
+ Hits 1539 1540 +1
Misses 238 238
Continue to review full report at Codecov.
|
|
I find that for large # of datapoints, GP is very slow. This pull request does not fix that. Anyone else seeing this issue? |
|
I think the fact that GPs slow down as the number of data points increases is one of the drawbacks of GPs. I tried to find the relevant bit of the scikit-learn docs that explains the scaling behaviour but I couldn't find it. |
|
Yup a normal thing for GP: https://arxiv.org/pdf/1502.05700.pdf see Figure 1 there @jonathanng maybe add this somewhere to the comments if you have time? Otherwise we could add it later |
|
I still think having a control over n_jobs would be very beneficial, esp. if you run multiple optimizations at the same time in order to test for example the algorithm |
| def __init__(self, dimensions, base_estimator="gp", | ||
| n_random_starts=None, n_initial_points=10, | ||
| acq_func="gp_hedge", | ||
| n_jobs=1, acq_func="gp_hedge", |
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.
Please add description of n_jobs to docstrings.
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.
+1
|
Beyond the |
No description provided.