Repository navigation
perf(ci): use ARM runners for builds and selected tests - #26106
Merged
Merged
Conversation
Co-Authored-By: OpenAI Codex <codex@openai.com>
Contributor
size-limit report 📦Compared: ba36175 (PR test merge using develop at a2dbec0) Against: eadbabb (develop) · base run #65073
|
Contributor
Optional E2E testsSome optional checks were not successful. They do not block the merge. 6 not successful, 50 successful. See the run.
Successful checks
|
Keep branch builds and SQL Server integration jobs on x86-64, and isolate architecture-specific caches. Co-Authored-By: OpenAI Codex <codex@openai.com>
Co-Authored-By: OpenAI Codex <codex@openai.com>
Co-Authored-By: OpenAI Codex <codex@openai.com>
Co-Authored-By: OpenAI Codex <codex@openai.com>
Co-Authored-By: OpenAI Codex <codex@openai.com>
Co-Authored-By: OpenAI Codex <codex@openai.com>
Co-Authored-By: OpenAI Codex <codex@openai.com>
Co-Authored-By: OpenAI Codex <codex@openai.com>
Co-Authored-By: OpenAI Codex <codex@openai.com>
nicohrubec
marked this pull request as ready for review
November 5, 2026 13:21
nicohrubec
requested review from
Lms24,
andreiborza,
chargome,
isaacs,
logaretm and
s1gr1d
and removed request for
a team
November 5, 2026 13:21
chargome
approved these changes
Nov 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Today our CI uses x86 runners for all our job, this PR moves a selection of our CI runners to the free ARM64 runners to reduce CI time. The jobs that are moved over were determined by doing a few benchmark runs with more details in the tables below.
x86 baseline is our CI as it runs today. The ARM run then uses ARM runners as much as possible with the caveat that we cannot move node/bun/deno integration tests to ARM atm because they run SQL Server container tests that do not work on ARM (potentially something we can look into next if we go with this). Running on ARM improves many jobs a lot but is worse for browser and E2E tests, partially because of missing cache hits. That's how I ended up with the "hybrid" configuration that basically takes best of both worlds.
In the table below you can see in more detail how the job timings changed between the configurations for the latest test run:
* Excludes initial queueing and optional jobs. Each run had one required-test failure; ARM browser caches were cold.
† These integration jobs stayed on x86 in both runs.