self-hosted-runners: use 4-core VMs #30
Merged
+2
−2
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.
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