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.

Sign up for GitHub

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

[Datasets] Note that explicit resource allocation is experimental, fix typos #25038

Merged
merged 1 commit into from
May 20, 2022
Merged

[Datasets] Note that explicit resource allocation is experimental, fix typos #25038

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
8 changes: 6 additions & 2 deletions doc/source/data/key-concepts.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -132,10 +132,14 @@ group by default. This can be thought of as Datasets requesting resources from t
margins of the cluster, outside of those ML library placement groups.

Although this is the default behavior, you can force all Datasets workloads to be
schedule without a placement group by specifying a placement group as the global
scheduled within a placement group by specifying a placement group as the global
scheduling strategy for all Datasets tasks/actors, using the global
:class:`DatasetContext <ray.data.DatasetContext>`:
:class:`DatasetContext <ray.data.DatasetContext>`.

.. note::

This is an experimental feature subject to change as we work to improve our
resource allocation model for Datasets.

.. literalinclude:: ./doc_code/key_concepts.py
:language: python
Expand Down