ray/ci/long_running_tests
Eric Liang dd70720578
[rllib] Rename sample_batch_size => rollout_fragment_length (#7503)
* bulk rename

* deprecation warn

* update doc

* update fig

* line length

* rename

* make pytest comptaible

* fix test

* fi sys

* rename

* wip

* fix more

* lint

* update svg

* comments

* lint

* fix use of batch steps
2020-03-14 12:05:04 -07:00
..
ray-project [core] Add long running regression test for distributed ref counting and fix memory leak (#7302) 2020-02-24 17:58:42 -08:00
workloads [rllib] Rename sample_batch_size => rollout_fragment_length (#7503) 2020-03-14 12:05:04 -07:00
.gitignore Switch cluster longevity tests to DLAMI, fix ray up verbosity (#5084) 2019-07-02 00:19:05 -07:00
README.rst Improve release process from 0.8.2 (#7303) 2020-02-24 21:18:53 -08:00

Long Running Tests
==================

This directory contains the long-running workloads which are intended to run
forever until they fail. To set up the project you need to run

.. code-block:: bash

    pip install anyscale
    anyscale project create


Running the Workloads
---------------------

You can start all the workloads with:

.. code-block:: bash

    anyscale session start -y run --workload="*" --wheel=https://s3-us-west-2.amazonaws.com/ray-wheels/releases/0.7.5/6da7eff4b20340f92d3fe1160df35caa68922a97/ray-0.7.5-cp36-cp36m-manylinux1_x86_64.whl

This will start one EC2 instance per workload and will start the workloads
running (one per instance). You can start a specific workload by specifying
its name as an argument ``--workload=`` instead of ``"*"``. A list of
available options is available via `any session start run --help`.


Check Workload Statuses
-----------------------

To check up on the workloads, run either
``anyscale session --name="*" execute check-load``, which
will print the load on each machine, or
``anyscale session --name="*" execute show-output``, which
will print the tail of the output for each workload.

To debug workloads that have failed, you may find it useful to ssh to the
relevant machine, attach to the tmux session (usually ``tmux a -t 0``), inspect
the logs under ``/tmp/ray/session*/logs/``, and also inspect
``/tmp/ray/session*/debug_state.txt``.

Shut Down the Workloads
-----------------------

The instances running the workloads can all be killed by running
``anyscale session stop --name "*"``.

Adding a Workload
-----------------

To create a new workload, simply add a new Python file under ``workloads/`` and
add the workload in the run command in `ray-project/project.yaml`.