When I do ray.put, what sized objects should I expect to stay local? Is there a way to control that explicitly? I would like the object to stay on one machine for locality.

From the Ray arch google doc, it seems to suggest that large objects get stored in the “distributed object store”. I don’t know what “large” means

Even it’s put into distributed object store, it’s still local and there is no copy that will happen.

To answer your original question, the threshold is defined here: ray-project/ray/blob/master/src/ray/common/ray_config_def.h#L147 /// even balancing of load. Low values (min 0.0) encourage more load spreading. RAY_CONFIG(float, scheduler_spread…

When you call ray.put, it is always put into the object store, and they are always local to nodes that call ray.put.

At what size will objects no longer use local storage

Ray Core

yic February 17, 2022, 9:13am 2

When you call ray.put, from my memory, it always stays on the node of the worker where it’s executed. @sangcho or @Chen_Shen may double confirm that.

Topic		Replies	Views
In-process object store of the driver process Ray Core	8	448	January 28, 2021
Avoid ray.put for arguments to remote actor Ray Core	1	362	April 5, 2022
Will it be stored in plasma regardless of the size of the data? Ray Core	4	669	November 25, 2021
Ray.put from Ray task - local or not Ray Core	9	658	March 15, 2021
Best practice for processing large amounts of data Ray Core	5	1300	April 10, 2022

At what size will objects no longer use local storage

Related topics