-
-
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
Task Annotations #2180
Task Annotations #2180
Conversation
0df5d99
to
6775c9c
Compare
92d4304
to
4b0a03d
Compare
@sjperkins thanks for this PR. I assume this is still a WIP based on the last few comments dask/dask#3783 . We are developing a benchmarks codebase: https://github.com/dask/dask-benchmarks and it would very interesting to evaluate this work with specific GPU workloads . I don't think there is anything to do in the near term and I'll ping back again once the benchmark repo has been flushed out |
Would it be helpful to resolve the conflicts with master? I've done this locally. The body of the following test seems to run, but seems to fail on shutting down the test cluster. /home/sperkins/work/ska/code/distributed/distributed/utils.py:134:
RuntimeWarning: Couldn't detect a suitable IP address for reaching '2001:4860:4860::8888', defaulting to '::1': [Errno 101] Network is unreachable That looks like an IPV6 address Expanded test output here:
|
@sjperkins this PR will take some time to properly review and one of the question we would want to answer before merging is whether or not there is any impact on performance. |
OK, I think the tests are currently failing (after the master merge) due to complex tasks which have changed a bit, especially handling the following case in args: distributed/distributed/client.py Lines 1633 to 1634 in 2f46ab1
let me spend some time getting the tests working, its been a year since I touched this PR. |
I wouldn't prioritize fixing tests and merging with master . It will be some time before we can look at this work. My intention in commenting yesterday was not to nudge you into more work, but rather explain why there wasn't a review. |
3a03dfb
to
f661bd9
Compare
I've merged master and simplified complex task handling. Previously, this was split over Most functionality has now been moved into I believe this is a reasonable compromise as complex tasks are generally created by the optimization process and, for the moment, I think it's reasonable to only use a single task annotation for a complex task. The alternative is for the scheduler to unpack the entire complex task to search for annotations, but this likely has further performance implications. I view the optimization step as a good place for future handling the removal/merging of annotations. Regardless, the PR in its current state should be sufficient for benchmarking/testing basic cases. |
Thanks for letting me know. I felt motivated to relook at the PR because it's been a year since it was created and wanted to refresh the issue in my mind. Don't feel pressure from my side, although I am interested to see how useful others might find the concept. |
f227eaf
to
f8f647d
Compare
This reverts commit 198c29e. dask/dask#6409
Closing this as we ended up going a different route for task annotations. Thanks @sjperkins! |
Dask Issue dask/dask#3783
Related dask PR dask/dask#3869