ray/release/benchmarks/app_config.yaml

base_image: {{ env["RAY_IMAGE_ML_NIGHTLY_GPU"] | default("anyscale/ray-ml:nightly-py37-gpu") }}
env_vars: {"LD_PRELOAD": "/usr/lib/x86_64-linux-gnu/libjemalloc.so"}

debian_packages:
- libjemalloc-dev

python:
  pip_packages: []
  conda_packages: []

post_build_cmds:
  - pip3 install tqdm || true
  - pip3 uninstall ray -y && pip3 install -U {{ env["RAY_WHEELS"] | default("ray") }}
  - {{ env["RAY_WHEELS_SANITY_CHECK"] | default("echo No Ray wheels sanity check") }}
[ci/release] Support running tests with different python versions (#24843) OSS release tests currently run with hardcoded Python 3.7 base. In the future we will want to run tests on different python versions. This PR adds support for a new `python` field in the test configuration. The python field will determine both the base image used in the Buildkite runner docker container (for Ray client compatibility) and the base image for the Anyscale cluster environments. Note that in Buildkite, we will still only wait for the python 3.7 base image before kicking off tests. That is acceptable, as we can assume that most wheels finish in a similar time, so even if we wait for the 3.7 image and kick off a 3.8 test, that runner will wait maybe for 5-10 more minutes. 2022-05-17 17:03:12 +01:00			`base_image: {{ env["RAY_IMAGE_ML_NIGHTLY_GPU"] \| default("anyscale/ray-ml:nightly-py37-gpu") }}`
[Core] install jemalloc in Ray docker and use jemalloc in `benchmark` release tests (#26112) There are mysterious memory usage growth in Ray clusters that disappear when running with jemalloc. Before we are able to figure out the root cause, it seems using jemalloc by default can be a good walkaround. Because of its efficiency, using jemalloc by default can be beneficial, but we need to run more benchmarks to verify. 2022-06-27 23:26:56 -07:00			`env_vars: {"LD_PRELOAD": "/usr/lib/x86_64-linux-gnu/libjemalloc.so"}`

			`debian_packages:`
			`- libjemalloc-dev`
Migrate scalability tests (#22901) This PR migrates scalability tests to the new infra. I had to copy the benchmarks folder to the release folder to make it work. I will remove some unnecessary files (e.g., benchmark.yaml or wait_for_cluster file) Alternatively we can support a different path than /release from the tool, but I think this way is cleaner. I am open to suggestion though cc @krfricke 2022-03-09 10:22:41 +09:00
			`python:`
			`pip_packages: []`
			`conda_packages: []`

			`post_build_cmds:`
			`- pip3 install tqdm \|\| true`
			`- pip3 uninstall ray -y && pip3 install -U {{ env["RAY_WHEELS"] \| default("ray") }}`
			`- {{ env["RAY_WHEELS_SANITY_CHECK"] \| default("echo No Ray wheels sanity check") }}`