ray/benchmarks/single_node.yaml

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

max_workers: 0

aws:
    BlockDeviceMappings:
        - DeviceName: /dev/sda1
          Ebs:
            VolumeSize: 500

head_node_type:
    name: head_node
    instance_type: m4.16xlarge
    resources:
      # 128 GB
      object_store_memory: 128000000000


worker_node_types:
    - name: worker_node
      instance_type: m5.2xlarge
      min_workers: 0
      max_workers: 0
      use_spot: false
Integrate scalability envelope with releaser (#16417) * . * . * . * . * . * . * . * success Co-authored-by: Alex Wu <alex@anyscale.com> 2021-06-15 10:42:55 -07:00			`cloud_id: {{env["ANYSCALE_CLOUD_ID"]}}`
			`region: us-west-2`

			`max_workers: 0`

			`aws:`
			`BlockDeviceMappings:`
			`- DeviceName: /dev/sda1`
			`Ebs:`
			`VolumeSize: 500`

			`head_node_type:`
			`name: head_node`
			`instance_type: m4.16xlarge`
			`resources:`
			`# 128 GB`
			`object_store_memory: 128000000000`


			`worker_node_types:`
			`- name: worker_node`
[Nightly test] Fix additional k8s issues + add new tests (#23231) Fix bug from the previous fixes. Add more tests Stop using m5.xlarge (not supported now) There are 2 hard blockers from the infra: 1. Large size disk is not supported. 2. m5.xlarge is not supported. Both are considered as a high priority to be fixed soon. 2022-03-17 08:37:29 +09:00			`instance_type: m5.2xlarge`
Integrate scalability envelope with releaser (#16417) * . * . * . * . * . * . * . * success Co-authored-by: Alex Wu <alex@anyscale.com> 2021-06-15 10:42:55 -07:00			`min_workers: 0`
			`max_workers: 0`
			`use_spot: false`