-
-
Notifications
You must be signed in to change notification settings - Fork 719
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
Ensure shuffle split operations are blacklisted from work stealing #4964
Conversation
If shuffle split tasks are not blacklisted from work stealing, this can have catastrophic effects on performance. See also dask#4962
Hrm, I wonder if we should just blacklist any task that runs very quickly 🤔 😄 |
cc @madsbk |
How quickly should it be? I've seen splits take longer than 5ms. I feel it is incredibly difficult to put a sane number on this but maybe you are right and something like |
I was joking. You removed this behavior in the work stealing PR, right? |
Does this fix #4962 ? |
Should this be merged? |
Ah, no. We also need to handle |
yes but that's only a draft and I want to reiterate what's going on after the sizes are properly measured.
Not yet, We'll need
I believe it will improve performance and stability. I would like to (eventually) get the system into a state where we don't need this but I believe we're not there, yet. |
See also dask/dask#7844 for summary and cause of the regression |
All tests green? That's a sign! (I swear, I didn't cheat) |
If shuffle split tasks are not blacklisted from work stealing, this can have
catastrophic effects on performance.
See also #4962