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
BENCH scaling of a GridSearch with n_jobs #1427
Conversation
Codecov ReportPatch coverage has no change and project coverage change:
Additional details and impacted files@@ Coverage Diff @@
## master #1427 +/- ##
==========================================
- Coverage 94.66% 94.61% -0.06%
==========================================
Files 45 44 -1
Lines 6918 7205 +287
==========================================
+ Hits 6549 6817 +268
- Misses 369 388 +19 see 6 files with indirect coverage changes Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report in Codecov by Sentry. |
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.
Very nice!
The bump between 6 and 8 jobs is quite curious.
7c2ff63
to
85b1d26
Compare
I messed up with git, but I finally pushed a simpler |
I think this kind of plots would be more informative as speed-ups factor vs a chosen baseline (e.g. the slowest or the single thread result from the current branch) but this is already useful as it is so I merged. |
Add a benchmark to compare
joblib
scaling for aGridSearch
on synthetic data.This benchmark allows to compare 2 versions of
joblib
by running it multiple times.