Priority families#6
Draft
gjoseph92 wants to merge 3 commits into
Draft
Conversation
problems: 1. widely-shared root tasks traverse up to the first dependent and join their family 2. wide fan-in tasks pull everything into their family
not actually using them for anything yet, but this is how it might work
Unit Test ResultsSee test report for an extended history of previous test failures. This is useful for diagnosing flaky tests. 15 files ± 0 15 suites ±0 7h 33m 48s ⏱️ + 50m 1s For more details on these failures, see this check. Results for commit ad83de3. ± Comparison against base commit 3a0329e. ♻️ This comment has been updated with latest results. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
My initial approach implementing the ideas from dask#7141. Just the core co-grouping algorithm, not actually used for scheduling at all yet.
I branched this off of dask#7076, since it might ultimately make some of the scheduling part easier, but it's not actually used here.
Haven't looked at dask#7141 much at all. Also not sure I implemented the algorithm correctly.
test_family_two_step_reduction_linear_chains.