From b1ab4c4eb0db9994cf7251676303944bbadcdcd2 Mon Sep 17 00:00:00 2001 From: Chirag Aggarwal Date: Sun, 20 Sep 2026 19:27:49 +0100 Subject: [PATCH] ci: move the runner presets to c3d n2d-standard-4 is EPYC Rome/Milan where RunsOn was handing out Zen 4, and these lanes are short and largely single-thread bound, so the core generation shows up directly: 42% slower than RunsOn on n2d against 21% on c3d, measured on #13779. Only the family changes, so every existing runner= keeps resolving. --- .github/gcrunner.yml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/.github/gcrunner.yml b/.github/gcrunner.yml index 60824c5b97..266c59e875 100644 --- a/.github/gcrunner.yml +++ b/.github/gcrunner.yml @@ -1,38 +1,38 @@ runners: small: - family: n2d + family: c3d cpu: 2+4 ram: 8+16 disk: 80gb standard: - family: n2d + family: c3d cpu: 4+8 ram: 16+32 disk: 80gb # The extra disk is the layer cache, not the workload. build: - family: n2d + family: c3d cpu: 8 ram: 32 disk: 100gb publish: - family: n2d + family: c3d cpu: 4 ram: 16 disk: 80gb e2e: - family: n2d + family: c3d cpu: 4+8 ram: 16+32 disk: 80gb # Databases and TablesDB run three paratest processes against every adapter. e2e-large: - family: n2d + family: c3d cpu: 8+16 ram: 32+64 disk: 80gb