[Data] Fix iter_tensor_batches_benchmark_multi_node GCE (#34598)

The `iter_tensor_batches_benchmark_multi_node` GCE variant was failing because it used the wrong compute config. Signed-off-by: Balaji Veeramani <[email protected]>
ray-project · Apr 20, 2023 · 42dd417 · 42dd417
1 parent e2ffa51
commit 42dd417
Show file tree

Hide file tree

Showing 2 changed files with 18 additions and 1 deletion.
diff --git a/release/nightly_tests/dataset/multi_node_benchmark_compute_gce.yaml b/release/nightly_tests/dataset/multi_node_benchmark_compute_gce.yaml
@@ -0,0 +1,17 @@
+cloud_id: {{env["ANYSCALE_CLOUD_ID"]}}
+region: us-west1
+allowed_azs:
+- us-west1-c
+
+max_workers: 0
+
+head_node_type:
+    name: head_node
+    instance_type: n2-standard-16 # m5.4xlarge
+
+worker_node_types:
+    - name: worker_node
+      instance_type: n2-standard-16 # m5.4xlarge
+      max_workers: 3
+      min_workers: 3
+      use_spot: false
diff --git a/release/release_tests.yaml b/release/release_tests.yaml
@@ -5169,7 +5169,7 @@
       frequency: manual
       cluster:
         cluster_env: app_config.yaml
-        cluster_compute: single_node_benchmark_compute_gce.yaml
+        cluster_compute: multi_node_benchmark_compute_gce.yaml
 
 - name: iter_batches_benchmark_single_node
   group: data-tests