Skip to content

Reduce dask.order overhead by removing stripped_dep computation #9031

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

Merged
merged 1 commit into from
Mar 26, 2025

Conversation

fjetter
Copy link
Member

@fjetter fjetter commented Mar 25, 2025

The order function has been ignoring this for a while. No reason to compute it

Copy link
Contributor

Unit Test Results

See test report for an extended history of previous test failures. This is useful for diagnosing flaky tests.

    27 files  ±0      27 suites  ±0   11h 47m 47s ⏱️ + 14m 17s
 4 106 tests ±0   3 989 ✅  - 3    112 💤 ±0  5 ❌ +3 
51 478 runs  ±0  49 163 ✅  - 3  2 310 💤 +1  5 ❌ +2 

For more details on these failures, see this check.

Results for commit 090db47. ± Comparison against base commit c5ca1ff.

@fjetter fjetter merged commit bda2d31 into dask:main Mar 26, 2025
28 of 34 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant