benchmarks workflow (facebook/stylex)
The benchmarks workflow from facebook/stylex, explained and optimized by Latchkey.
CI health: C - fair
Point runs-on at Latchkey and get run de-duplication, job timeouts, SHA-pinned actions, self-healing for flaky steps, and up to 58% lower cost, applied automatically.
What it does
This is the benchmarks workflow from the facebook/stylex repository, a real project running GitHub Actions. It is shown here with attribution under its MIT license.
Below, Latchkey shows a faster, safer version produced by its optimization engine.
The workflow
name: benchmarks
on: [pull_request]
jobs:
perf:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v6
with:
fetch-depth: 50
- uses: actions/setup-node@v6
with:
node-version: '22.x'
cache: 'yarn'
cache-dependency-path: yarn.lock
- run: corepack prepare yarn@1.22.22 --activate
- name: 'Setup temporary files'
run: |
echo "BASE_JSON=$(mktemp)" >> $GITHUB_ENV
echo "PATCH_JSON=$(mktemp)" >> $GITHUB_ENV
- name: 'Benchmark base'
run: |
git checkout -f ${{ github.event.pull_request.base.sha }}
git clean -fdx
yarn install --frozen-lockfile --silent
if yarn workspace benchmarks run perf -- -o ${{ env.BASE_JSON }}; then
echo "Ran successfully on base branch"
else
echo "{}" > ${{ env.BASE_JSON }} # Empty JSON as default
echo "Benchmark script not found on base branch, using default values"
fi
- name: 'Benchmark patch'
run: |
git checkout -f ${{ github.event.pull_request.head.sha }}
git clean -fdx
yarn install --frozen-lockfile --silent
yarn workspace benchmarks run perf -- -o ${{ env.PATCH_JSON }}
echo "Ran successfully on patch branch"
- name: 'Collect results'
id: collect
run: |
echo "table<<EOF" >> $GITHUB_OUTPUT
yarn workspace benchmarks run compare -- ${{ env.BASE_JSON }} ${{ env.PATCH_JSON }} >> markdown
cat markdown >> $GITHUB_OUTPUT
echo "EOF" >> $GITHUB_OUTPUT
- name: 'Post comment'
uses: edumserrano/find-create-or-update-comment@v3
with:
issue-number: ${{ github.event.pull_request.number }}
body-includes: '<!-- workflow-benchmarks-perf-data -->'
comment-author: 'github-actions[bot]'
body: |
<!-- workflow-benchmarks-perf-data -->
### workflow: benchmarks/perf
Comparison of performance test results, measured in operations per second. Larger is better.
${{ steps.collect.outputs.table }}
edit-mode: replace
size:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v6
with:
fetch-depth: 50
- uses: actions/setup-node@v6
with:
node-version: '22.x'
cache: 'yarn'
cache-dependency-path: yarn.lock
- run: corepack prepare yarn@1.22.22 --activate
- name: 'Setup temporary files'
run: |
echo "BASE_JSON=$(mktemp)" >> $GITHUB_ENV
echo "PATCH_JSON=$(mktemp)" >> $GITHUB_ENV
- name: 'Benchmark base'
run: |
git checkout -f ${{ github.event.pull_request.base.sha }}
git clean -fdx
yarn install --frozen-lockfile --silent
if yarn workspace benchmarks run size -- -o ${{ env.BASE_JSON }}; then
echo "Ran successfully on base branch"
else
echo "{}" > ${{ env.BASE_JSON }} # Empty JSON as default
echo "Benchmark script not found on base branch, using default values"
fi
- name: 'Benchmark patch'
run: |
git checkout -f ${{ github.event.pull_request.head.sha }}
git clean -fdx
yarn install --frozen-lockfile --silent
yarn workspace benchmarks run size -- -o ${{ env.PATCH_JSON }}
echo "Ran successfully on patch branch"
- name: 'Collect results'
id: collect
run: |
echo "table<<EOF" >> $GITHUB_OUTPUT
yarn workspace benchmarks run compare -- ${{ env.BASE_JSON }} ${{ env.PATCH_JSON }} >> markdown
cat markdown >> $GITHUB_OUTPUT
echo "EOF" >> $GITHUB_OUTPUT
- name: 'Post comment'
uses: edumserrano/find-create-or-update-comment@v3
with:
issue-number: ${{ github.event.pull_request.number }}
body-includes: '<!-- workflow-benchmarks-size-data -->'
comment-author: 'github-actions[bot]'
body: |
<!-- workflow-benchmarks-size-data -->
### workflow: benchmarks/size
Comparison of minified (terser) and compressed (brotli) size results, measured in bytes. Smaller is better.
${{ steps.collect.outputs.table }}
edit-mode: replace
The same workflow, on Latchkey
Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.
name: benchmarks on: [pull_request] concurrency: group: ${{ github.workflow }}-${{ github.ref }} cancel-in-progress: true jobs: perf: timeout-minutes: 30 runs-on: latchkey-small steps: - uses: actions/checkout@v6 with: fetch-depth: 50 - uses: actions/setup-node@v6 with: node-version: '22.x' cache: 'yarn' cache-dependency-path: yarn.lock - run: corepack prepare yarn@1.22.22 --activate - name: 'Setup temporary files' run: | echo "BASE_JSON=$(mktemp)" >> $GITHUB_ENV echo "PATCH_JSON=$(mktemp)" >> $GITHUB_ENV - name: 'Benchmark base' run: | git checkout -f ${{ github.event.pull_request.base.sha }} git clean -fdx yarn install --frozen-lockfile --silent if yarn workspace benchmarks run perf -- -o ${{ env.BASE_JSON }}; then echo "Ran successfully on base branch" else echo "{}" > ${{ env.BASE_JSON }} # Empty JSON as default echo "Benchmark script not found on base branch, using default values" fi - name: 'Benchmark patch' run: | git checkout -f ${{ github.event.pull_request.head.sha }} git clean -fdx yarn install --frozen-lockfile --silent yarn workspace benchmarks run perf -- -o ${{ env.PATCH_JSON }} echo "Ran successfully on patch branch" - name: 'Collect results' id: collect run: | echo "table<<EOF" >> $GITHUB_OUTPUT yarn workspace benchmarks run compare -- ${{ env.BASE_JSON }} ${{ env.PATCH_JSON }} >> markdown cat markdown >> $GITHUB_OUTPUT echo "EOF" >> $GITHUB_OUTPUT - name: 'Post comment' uses: edumserrano/find-create-or-update-comment@v3 with: issue-number: ${{ github.event.pull_request.number }} body-includes: '<!-- workflow-benchmarks-perf-data -->' comment-author: 'github-actions[bot]' body: | <!-- workflow-benchmarks-perf-data --> ### workflow: benchmarks/perf Comparison of performance test results, measured in operations per second. Larger is better. ${{ steps.collect.outputs.table }} edit-mode: replace size: timeout-minutes: 30 runs-on: latchkey-small steps: - uses: actions/checkout@v6 with: fetch-depth: 50 - uses: actions/setup-node@v6 with: node-version: '22.x' cache: 'yarn' cache-dependency-path: yarn.lock - run: corepack prepare yarn@1.22.22 --activate - name: 'Setup temporary files' run: | echo "BASE_JSON=$(mktemp)" >> $GITHUB_ENV echo "PATCH_JSON=$(mktemp)" >> $GITHUB_ENV - name: 'Benchmark base' run: | git checkout -f ${{ github.event.pull_request.base.sha }} git clean -fdx yarn install --frozen-lockfile --silent if yarn workspace benchmarks run size -- -o ${{ env.BASE_JSON }}; then echo "Ran successfully on base branch" else echo "{}" > ${{ env.BASE_JSON }} # Empty JSON as default echo "Benchmark script not found on base branch, using default values" fi - name: 'Benchmark patch' run: | git checkout -f ${{ github.event.pull_request.head.sha }} git clean -fdx yarn install --frozen-lockfile --silent yarn workspace benchmarks run size -- -o ${{ env.PATCH_JSON }} echo "Ran successfully on patch branch" - name: 'Collect results' id: collect run: | echo "table<<EOF" >> $GITHUB_OUTPUT yarn workspace benchmarks run compare -- ${{ env.BASE_JSON }} ${{ env.PATCH_JSON }} >> markdown cat markdown >> $GITHUB_OUTPUT echo "EOF" >> $GITHUB_OUTPUT - name: 'Post comment' uses: edumserrano/find-create-or-update-comment@v3 with: issue-number: ${{ github.event.pull_request.number }} body-includes: '<!-- workflow-benchmarks-size-data -->' comment-author: 'github-actions[bot]' body: | <!-- workflow-benchmarks-size-data --> ### workflow: benchmarks/size Comparison of minified (terser) and compressed (brotli) size results, measured in bytes. Smaller is better. ${{ steps.collect.outputs.table }} edit-mode: replace
What changed
- Run on Latchkey managed runners with one line (
runs-on), which apply the fixes below automatically and self-heal transient failures. This example useslatchkey-small; pick the runner size that fits the job. - Cancel superseded runs when a branch or PR gets a newer push.
- Add a job timeout so a hung step cannot burn hours of runner time.
1 third-party action is referenced by a movable tag. Pin it to the commit SHA (Latchkey resolves and applies this automatically) so a repointed tag cannot change what runs.
What Latchkey heals here
This workflow has steps that commonly fail on transient issues (network, registries, flaky browsers). On Latchkey managed runners they are detected, retried, and self-healed instead of failing your build:
- Dependency installs
This workflow runs 2 jobs per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.