| [core] Migrate wait_for_condition and async_wait_for_condition from _private to _common (#53652) Fixes #53478 --------- Signed-off-by: abrar <abrar@anyscale.com> Signed-off-by: Edward Oakes <ed.nmi.oakes@gmail.com> Co-authored-by: Edward Oakes <ed.nmi.oakes@gmail.com> | 1 年前 |
| [core] Large objects release test (#51625) To have an ongoing benchmark that tests the time it takes to send a 4GB object to 9 nodes. And the time it takes to ingest 4gb objects from 9 other nodes. --------- Signed-off-by: dayshah <dhyey2019@gmail.com> | 1 年前 |
| move signal and semaphore to _common/ (#53457) Fixes: https://github.com/ray-project/ray/issues/53478 --------- Signed-off-by: abrar <abrar@anyscale.com> | 1 年前 |
| [core] Update the scalability envelop (#32131) With the recent updating of the nightly tests, update the data here. In the nightly tests, we use 2k nodes (2cpus per node) and 20k actors, but if better node is used, we can run more than 40k actors. https://buildkite.com/ray-project/release-tests-branch/builds/1321#018604d7-86a3-4fad-ac6c-803db73821d3 | 3 年前 |
| 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 | 4 年前 |
| Add GCE variation for core release tests [3/n] (#34425) - microbenchmark_38 - shuffle_20gb_with_state_api - object_store - many_actors - many_tasks - many_pgs - chaos_many_tasks_no_object_store - chaos_many_actors Signed-off-by: Jiajun Yao <jeromeyjj@gmail.com> | 3 年前 |
| 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 | 4 年前 |
| [core] Stabilize many_nodes release test (#49193) Signed-off-by: dayshah <dhyey2019@gmail.com> | 1 年前 |
| [CI] Add GCE variation for core release tests [1/n] (#34065) many_nodes, pg_autoscaling_regression_test, single_node Signed-off-by: Jiajun Yao <jeromeyjj@gmail.com> | 3 年前 |
| [core] Change m4's to m6i's for core release tests (#48753) Signed-off-by: dayshah <dhyey2019@gmail.com> | 1 年前 |
| Add GCE variation for core release tests [3/n] (#34425) - microbenchmark_38 - shuffle_20gb_with_state_api - object_store - many_actors - many_tasks - many_pgs - chaos_many_tasks_no_object_store - chaos_many_actors Signed-off-by: Jiajun Yao <jeromeyjj@gmail.com> | 3 年前 |
| use smaller instance for scheduling tests (#25635) m5.16xlarge instances have 64 CPU and 256GB memory, which are overkill for scheduling tests that do not have a lot of computations. Use smaller instance m5.4xlarge to save cost and make allocating instances easier. | 4 年前 |
| [Release Test] Add GCE variation for core release tests [4/n] (#34442) - dask_on_ray_100gb_sort - stress_test_state_api_scale - stress_test_many_tasks - stress_test_dead_actors - threaded_actors_stress_test - many_nodes_actor_test_on_v2 - placement_group_performance_test - scheduling_test_many_0s_tasks_many_nodes - agent_stress_test Signed-off-by: Jiajun Yao <jeromeyjj@gmail.com> | 3 年前 |
| [Release] Rename aws to advanced_configurations_json in compute config (#48809) Signed-off-by: Jiajun Yao <jeromeyjj@gmail.com> | 1 年前 |
| [Release Test] Add GCE variation for core release tests [2/n] (#34337) - single_node_oom - benchmark_worker_startup - Removed worker node types with max_worker = 0 Signed-off-by: Jiajun Yao <jeromeyjj@gmail.com> | 3 年前 |