-
Notifications
You must be signed in to change notification settings - Fork 207
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use arm runners #622
Use arm runners #622
Conversation
This needs some more work. While this speeds up uncached builds so they only take 20 minutes instead of 2-3 hours, for cached builds there is very little difference in build time. That little difference in build time is however 7-14x more expensive because the builds are using non-free runners. |
This pull request is stale because it has been open for 30 days with no activity. It will be closed in 30 days unless the stale label is removed. |
This pull request is stale because it has been open for 30 days with no activity. It will be closed in 30 days unless the stale label is removed. |
01649a0
to
1028b76
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't understand all the details here but the code looks like benign build plumbing and I trust that you're pursuing a noble goal with it.
What
Use arm64 runners to build core, rpc, and xdr-cli.
Uses free amd64 instances to first attempt to recover previously build core, rpc, and xdr-cli binaries from the GitHub Action cache.
Horizon, friendbot, and the quickstart image itself are still built only with free amd64 runners, because there doesn't appear to be a significant need to optimise those which would add additional cost.
Why
More efficient arm builds without needing emulation.
Lately core, now that it has all the rust components to build, has been taking a long time and struggling in many instances to build successfully. This changes brings core build time down to a consistent 20mins on the 4-core arm64 instance.
The workflow has many individual steps because building a single dependency like core first spins up a free amd64 instance to check the cache and load the image from there, and then the more expensive arm64 instance is only triggered when we actually need to build.
Trying It Out