Skip to content

self-hosted-runners: use 4-core VMs #30

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

Merged
merged 1 commit into from
Feb 11, 2023
Merged

self-hosted-runners: use 4-core VMs #30

merged 1 commit into from
Feb 11, 2023

Conversation

dennisameling
Copy link
Contributor

In a recent Actions run, we ran into the CPU quotum that was set in Azure (max. 20 cores across all active VMs). By lowering the vCPU count on the VMs from 8 to 4, we can increase the number of simultaneous VMs from 2 to 5.

Next to that, the current performance is mostly limited by x64-emulation of unixy-tools like Bash anyway. The workflows really aren't using all the CPU cores, only during things like Clang-compilation.

Ref: https://github.com/git-for-windows/git-for-windows-automation/actions/runs/4144779320/jobs/7168260908

In a recent Actions run, we ran into the CPU quotom that was set in
Azure (max. 20 cores across all active VMs). By lowering the vCPU count
on the VMs from 8 to 4, we can increase the number of simultaneous VMs
from 2 to 5.

Ref: https://github.com/git-for-windows/git-for-windows-automation/actions/runs/4144779320/jobs/7168260908
Signed-off-by: Dennis Ameling <[email protected]>
Copy link
Member

@dscho dscho left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great!

We may want to consider teaching the GitForWindowsHelper GitHub App to pay attention to the total number of currently-running Windows/ARM64 jobs and hold off creating new VMs accordingly (probably using successful delete-self-hosted-runner jobs as trigger to see whether a held-off creation needs to be started).

But that sounds a bit complex to set up and make robust, so let's only do this if we really need to (read: if we run into this so often that manual VM creations become too tedious).

@dscho dscho merged commit 4bc8132 into main Feb 11, 2023
@dscho dscho deleted the lower-cpu-count branch February 11, 2023 07:01
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.

2 participants