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.
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