ray/release/benchmarks/object_store.yaml

cloud_id: {{env["ANYSCALE_CLOUD_ID"]}}
region: us-west-2

max_workers: 49

head_node_type:
    name: head_node
    instance_type: m4.16xlarge
    resources:
      custom_resources:
        node: 1

worker_node_types:
    - name: worker_node
      instance_type: m4.2xlarge
      min_workers: 49
      max_workers: 49
      use_spot: false
      resources:
        custom_resources:
          node: 1
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			`cloud_id: {{env["ANYSCALE_CLOUD_ID"]}}`
			`region: us-west-2`

			`max_workers: 49`

			`head_node_type:`
			`name: head_node`
			`instance_type: m4.16xlarge`
			`resources:`
			`custom_resources:`
			`node: 1`

			`worker_node_types:`
			`- name: worker_node`
[Nightly tests] Improve k8s testing (#23108) This PR improves broken k8s tests. Use exponential backoff on the unstable HTTP path (getting job status sometimes has broken connection from the server. I couldn't really find the relevant logs to figure out why this is happening, unfortunately). Fix benchmark tests resource leak check. The existing one was broken because the job submission uses 0.001 node IP resource, which means the cluster_resources can never be the same as available resources. I fixed the issue by not checking node IP resources K8s infra doesn't support instances < 8 CPUs. I used m5.2xlarge instead of xlarge. It will increase the cost a bit, but it wouldn't be very big. 2022-03-14 19:49:15 +09:00			`instance_type: m4.2xlarge`
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			`min_workers: 49`
			`max_workers: 49`
			`use_spot: false`
			`resources:`
			`custom_resources:`
			`node: 1`