From 6c099c2e6043e079b1ce44e370d3fb5e09abd0e7 Mon Sep 17 00:00:00 2001 From: Sam Xie Date: Fri, 9 Aug 2024 11:27:56 -0700 Subject: [PATCH] Use self hosted runner to run benchmark (#5695) Part of #4537 These are some benchmark results from the `actuated` runner. It is pretty clear to me that this runner does not have a stable environment to produce stable benchmark results: - https://github.com/open-telemetry/opentelemetry-go/actions/runs/10278899889 - https://github.com/open-telemetry/opentelemetry-go/actions/runs/10275384692 Thus, I am switching the runner to the self-hosted runner, which uses bare metal, to run benchmarks. This is the request to use this type of runner. https://github.com/open-telemetry/community/issues/2266 The underlying machine is m3.small.x86. It has 8 cores 64 GiB. https://deploy.equinix.com/product/servers/m3-small/ --- This is an example of using this runner from otel java. https://github.com/open-telemetry/opentelemetry-java/actions/runs/10277337397/job/28439208528 --- This runner cannot be triggered on a forked repo: https://github.com/XSAM/opentelemetry-go/commit/faab7b90979749b5f01fb0dd9522bbcfaedd5854. So, it is quite safe if we only let it run on the main branch. --- .github/workflows/benchmark.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/benchmark.yml b/.github/workflows/benchmark.yml index d314e06c7af..dc7ad0af2c9 100644 --- a/.github/workflows/benchmark.yml +++ b/.github/workflows/benchmark.yml @@ -10,7 +10,7 @@ env: jobs: benchmark: name: Benchmarks - runs-on: actuated-arm64-4cpu-16gb + runs-on: self-hosted steps: - uses: actions/checkout@v4 - uses: actions/setup-go@v5