From 087186029ff9913fc19cba05c93b8ae5765e48f2 Mon Sep 17 00:00:00 2001 From: Matthias Frei Date: Thu, 21 Dec 2023 20:14:45 +0100 Subject: [PATCH] doc: update buildkite instance type (#4459) Documenting that we've bumped the buildkite instance type from t3 to m6i. The main reason for the switch is that the "burstable" nature of the t*-instances makes them extremely unsuitable for running benchmarks. The m6i are also much faster, but not much more expensive. Also, the agent pool is now at most 6 agents. Spinning up 10 agents and having to warm up all the caches, and then scaling back in after a single build, seemed excessive. --- doc/dev/testing/buildkite.rst | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/doc/dev/testing/buildkite.rst b/doc/dev/testing/buildkite.rst index c7cd1f1bd7..195afed734 100644 --- a/doc/dev/testing/buildkite.rst +++ b/doc/dev/testing/buildkite.rst @@ -89,7 +89,8 @@ Cluster configuration The agent cluster is operated by the SCION Association, in the AWS account ``scion-association``. - Primary contact `matzf `_, alt contact `nicorusti `_. + Primary contacts `matzf `_, `jiceatscion `_, + alt contact `nicorusti `_. The agent cluster is based on the `buildkite AWS CloudFormation template `_. @@ -99,7 +100,7 @@ Excerpt of the most relevant parameters: # Instance Configuration: ImageId: "" # use default machine image based on Amazon Linux 2 - InstanceType: t3.2xlarge # 8 vCPUs, 32GiB memory + InstanceType: m6i.2xlarge # 8 vCPUs, 32GiB memory RootVolumeSize: 100 RootVolumeType: gp3 BuildkiteAdditionalSudoPermissions: ALL # allow any sudo commands in pipeline @@ -107,7 +108,7 @@ Excerpt of the most relevant parameters: # Auto-scaling Configuration: MinSize: 0 - MaxSize: 10 + MaxSize: 6 ScaleInIdlePeriod: 600 # shut down after 10 minutes idle - ScaleOutFactor: 0.5 + ScaleOutFactor: 1.0 OnDemandPercentage: 0 # use only spot instances