ray.data.ExecutionOptions#
- class ray.data.ExecutionOptions(resource_limits: ExecutionResources | None = None, exclude_resources: ExecutionResources | None = None, preserve_order: bool = False, actor_locality_enabled: bool = True, verbose_progress: bool | None = None, label_selector: Dict[str, str] | None = None)[source]#
Bases:
objectCommon options for execution.
Some options may not be supported on all executors (e.g., resource limits).
- resource_limits#
Set a limit on the logical resources a Dataset can use. Autodetected by default.
- exclude_resources#
Amount of resources to exclude from Ray Data. Set this if you have other workloads running on the same cluster. Note, - If using Ray Data with Ray Train, training resources are automatically reserved and you don’t need to set exclude_resources for them. - For each resource type, resource_limits and exclude_resources can not be both set.
- preserve_order#
Set this to preserve the ordering between blocks processed by operators. Off by default.
- actor_locality_enabled#
Whether to enable locality-aware task dispatch to actors (off by default). This parameter applies to both stateful map and streaming_split operations.
- verbose_progress#
Whether to report progress individually per operator. By default, only AllToAll operators and global progress is reported. This option is useful for performance debugging. On by default.
- label_selector#
A mapping of label key to label value. When set, every task and actor launched by this Dataset (including shuffle, sort, and aggregator actors) carries this label selector in its remote args, constraining placement to nodes whose labels satisfy the selector. Used to scope a Dataset to a labeled subset of the cluster (e.g.
{"__subcluster__": "training"}). Operator-levellabel_selectorentries inray_remote_argstake precedence on key conflicts so existing node-pin selectors are preserved.
DeveloperAPI: This API may change across minor Ray releases.