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)	2018-12-14 23:49:37 -05:00
build-wheel-manylinux1.sh	Update arrow to reduce plasma IPCs. (#3497)	2018-12-14 23:49:37 -05:00
README-benchmarks.rst	[rllib][asv] Support ASV for RLlib (#2304)	2018-06-28 17:20:09 -07:00
README-building-wheels.md	[DataFrame] Add Parquet Support in Build Process (#1531)	2018-02-16 07:18:42 -08:00
setup.py	Ensure numpy is at least 1.10.4 in setup.py (#2462)	2018-12-24 11:01:25 -08:00