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. |
GaelVaroquaux
left a comment
There was a problem hiding this comment.
Very nice!
The bump between 6 and 8 jobs is quite curious.
|
Thanks, here is what I get on my laptop with 4 performance cores and 4 efficiency cores.
I cannot reproduce the plateauing effect in thomas' plot. |
|
Here is the same result with a
I find it less misleading. |
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
joblibscaling for aGridSearchon synthetic data.This benchmark allows to compare 2 versions of
joblibby running it multiple times.