9 ms·
Our use case is we're running around 30 GitHub Actions runners on VMs that are just building code in MATLAB. 'Full load' is => all the runners are occupied, CPU
by aetherspawn 4y ago
Our use case is we're running around 30 GitHub Actions runners on VMs that are just building code in MATLAB. 'Full load' is => all the runners are occupied, CPU shows around 50% on the host.
The idle case on the Intel server is RHEL OS running several Windows VMs that are doing nothing, and the loaded case is when we spin up a large VM with around 40 cores on that host and run something in MATLAB (essentially a similar job to what the runners would otherwise be running).
The comparison is not completely accurate, but our experience was only anecdotal.