Skip to content
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

Expose message-bytes-limit in config #7074

Merged
merged 2 commits into from
Sep 27, 2022

Conversation

hendrikmakait
Copy link
Member

@hendrikmakait hendrikmakait commented Sep 27, 2022

Addresses

Conflicts with

  • Tests added / passed
  • Passes pre-commit run --all-files

@@ -339,6 +339,17 @@ properties:
To avoid this, Dask usually used a file-based lock.
However, on some systems file-based locks don't work.
This is particularly common on HPC NFS systems, where users may want to set this to false.
transfer:
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

XREF: #6977

I went with singular transfer to be coherent with variable naming.

@@ -1129,7 +1130,7 @@ class WorkerState:
#: :meth:`BaseWorker.gather_dep`. Multiple small tasks that can be fetched from the
#: same worker will be clustered in a single instruction as long as their combined
#: size doesn't exceed this value.
transfer_message_target_bytes: int
transfer_message_bytes_limit: float
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Driveby: Renamed to match other attribute names (e.g., transfer_incoming_bytes_limit). cc @crusaderky

@github-actions
Copy link
Contributor

Unit Test Results

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

       15 files  ±0         15 suites  ±0   6h 15m 28s ⏱️ -19s
  3 116 tests ±0    3 029 ✔️  - 1    86 💤 +1  1 ±0 
23 064 runs  ±0  22 156 ✔️  - 1  907 💤 +1  1 ±0 

For more details on these failures, see this check.

Results for commit 71df3cd. ± Comparison against base commit 9038c7a.

@hendrikmakait hendrikmakait marked this pull request as ready for review September 27, 2022 10:12
@hendrikmakait
Copy link
Member Author

@hendrikmakait hendrikmakait self-assigned this Sep 27, 2022
@crusaderky crusaderky self-requested a review September 27, 2022 14:55
- string
- integer
description: |
The maximum size of a message sent between workers
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This description is not correct, no? Rather, IIUC, this is the maximum amount of "extra" data we'll ask for from a worker once we've picked a worker to transfer a task from.

So an individual message may be (much) larger than message-bytes-limit, but if we decide to glue a bunch of messages together into one gather the sum of the size of those messages will never exceed message-bytes-limit.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It does not explain the fine print, that's a fair point. I'll file a follow-up PR that highlights that this is not an absolute maximum.

@crusaderky crusaderky merged commit 8c4133c into dask:main Sep 27, 2022
@crusaderky
Copy link
Collaborator

thank you!

gjoseph92 pushed a commit to gjoseph92/distributed that referenced this pull request Oct 31, 2022
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.

3 participants