Skip to content
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 larger GitHub runners for build actions #1964

Closed
wants to merge 2 commits into from
Closed

Conversation

mgeisler
Copy link
Collaborator

@mgeisler mgeisler commented Apr 7, 2024

We apparently have access to larger runners on the GitHub Enterprise plan.

We apparently have access to larger runners on the GitHub Enterprise
plan.
@mgeisler
Copy link
Collaborator Author

mgeisler commented Apr 7, 2024

The standard GitHub-hosted runners have 4 cores for Linux.

Using the 64-core runner removes ~1 minute for the per-language builds. Compare

So the time per language shrinks from about 4.5 minutes to 3.5 minutes. This is not super impressive and I guess this is mainly because we have lots of serial work in our jobs: building the and testing the translation takes the same amount of time in both cases. It's basically only the cargo install steps that improve because of much better parallelism.

I'm now testing the publish workflow, but I expect similar results since this also mostly consist of single-threaded steps.

@mgeisler
Copy link
Collaborator Author

mgeisler commented Apr 7, 2024

The two publish jobs:

  • Before: 17m 16s in total, 23s used for uploading the page.
  • After, this PR: 17m 6s in total, without uploading the page.

I think this means that it's not worth using the larger runners for us.

@mgeisler mgeisler closed this Apr 7, 2024
@mgeisler
Copy link
Collaborator Author

mgeisler commented Apr 7, 2024

cc @qwandor, @djmitche, @randomPoison in case you had been wanting to experiment this this.

@mgeisler mgeisler deleted the ci-runners branch May 28, 2024 08:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant