ray/python at 681e8cd3fd17ec003115aa473d61a6916e8235a8 - ray

mirror of https://github.com/wassname/ray.git synced 2026-06-28 03:50:55 +08:00

Files

T

mattearllongshot 681e8cd3fd [autoscaler] Add an initial_workers option (#3530 )

## What do these changes do?

    This option goes along with `min_workers`, and `max_workers`.  When the
    cluster is first brought up (or when it is refreshed with a subsequent
    `ray up`) this number of nodes will be started.
    
    It's a workaround for issues of scaling (see related issues) where it
    can take a long time (or forever in the case where the head node has
    `--num-cpus 0`) to scale up a cluster in response to increasing demand.


## Related issue number

Workaround for https://github.com/ray-project/ray/issues/3339 and https://github.com/ray-project/ray/issues/2106

2019-01-05 17:58:42 -08:00

benchmarks

Deprecate num_workers argument to ray.init and ray start. (#3114 )

2018-10-28 20:12:49 -07:00

ray

[autoscaler] Add an initial_workers option (#3530 )

2019-01-05 17:58:42 -08:00

asv.conf.json

[asv] Pushing to s3 (#2246 )

2018-06-20 10:43:44 -07:00

build-wheel-macos.sh

Update arrow to reduce plasma IPCs. (#3497 )