Skip to content

Note queuing default change in changelog #7314

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 4 commits into from
Nov 16, 2022
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions docs/source/changelog.rst
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,16 @@ Changelog

Released on November 15, 2022

.. note::

This release changes the default scheduling mode to use :ref:`queuing <queuing>`.
This will significantly reduce cluster memory use in most cases, and generally
improve stability and performance. `Learn more here <https://www.coiled.io/blog/reducing-dask-memory-usage>`_
and please provide any feedback `on this discussion <https://github.com/dask/distributed/discussions/7128>`_.

In rare cases, this could make some workloads slower. See the :ref:`documentation <adjust-queuing>`
for more information, and how to switch back to the old mode.

New Features
^^^^^^^^^^^^
- Add ``ForwardOutput`` worker plugin to forward ``stdout`` and ``stderr`` to client. (:pr:`7297`) `Hendrik Makait`_
Expand Down
4 changes: 2 additions & 2 deletions docs/source/scheduling-policies.rst
Original file line number Diff line number Diff line change
Expand Up @@ -264,8 +264,8 @@ Adjusting or disabling queuing
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

*It's rare to need to adjust queuing. The default value works well for almost all cases.
Only advanced users wanting to tune performance in unusual cases might consider adjusing
this parameter.*
*Only advanced users wanting to tune performance in unusual cases might consider
*adjusting this parameter.*

Queuing behavior is controlled by the ``distributed.scheduler.worker-saturation`` config
value. This is set via the :doc:`Dask configuration system <configuration>`. The config
Expand Down