feat: improved DaskExecutor scheduling logic #1468
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a new implementation of the DaskExecutor scheduling logic. The logic is as follows:
Also:
Breaks/deprecates:
worker_affinityuse_dataframesUsage:
Example outputs with a random failure coffea processor:

Can be used for what #1393 wishes for, i.e.:
which should enable a more robust processing workflow.
Opening this in Draft mode as it breaks two kwargs and probably you want to test it first yourself. I wanted to write this down and have this diff somewhere as we're going to try this in the integration challenge.
cc @alexander-held @MoAly98 @oshadura @ArturU043