Commit graph

9 commits

Author SHA1 Message Date
Simon Mo
29b08ddc09
Improve release process from 0.8.2 (#7303) 2020-02-24 21:18:53 -08:00
Philipp Moritz
dd27bfbb75
Rename .rayproject to ray-project (#6278) 2019-12-05 16:15:42 -08:00
Philipp Moritz
57a5871ea6
Convert long running stress tests to projects (#5641) 2019-09-26 11:25:09 -07:00
Robert Nishihara
851c5b2dae Add a script for benchmarking performance for Ray developers. (#5472) 2019-08-19 23:41:23 -07:00
Eric Liang
5ab5017c67
[rllib] Fix impala stress test (#5101)
* add copy

* upgrade to tf 1.14

* update

* reduce count to workaround https://github.com/ray-project/ray/issues/5125

* Update impala.py

* placeholder

* comments

* update
2019-07-09 20:22:30 -07:00
Robert Nishihara
bcc379556b Make some fixes to long running stress tests. (#5056) 2019-06-28 15:42:54 -07:00
Eric Liang
6e3384a719
[rllib] Add three new long-running stress tests {APEX, IMPALA, PBT} (#4215) 2019-03-04 14:05:42 -08:00
Robert Nishihara
c4aa90314d Add script for shutting down tests. (#4203) 2019-03-01 19:56:30 -08:00
Robert Nishihara
75504b9586 Add script for running infinitely long stress tests. (#4163)
Running `./ci/long_running_tests/start_workloads.sh` will start several workloads running (each in their own EC2 instance).
- The workloads run forever.
- The workloads all simulate multiple nodes but use a single machine.
- You can get the tail of each workload by running `./ci/long_running_tests/check_workloads.sh`.
- You have to manually shut down the instances.

As discussed with @ericl @richardliaw, the idea here is to optimize for the debuggability of the tests. If one of them fails, you can ssh to the relevant instance and see all of the logs.
2019-02-27 14:33:06 -08:00