|
From: | Paolo Bonzini |
Subject: | Re: Serious doubts about Gitlab CI |
Date: | Fri, 19 Mar 2021 10:41:46 +0100 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.0 |
On 19/03/21 10:33, Stefan Hajnoczi wrote:
On Thu, Mar 18, 2021 at 09:30:41PM +0100, Paolo Bonzini wrote:On 18/03/21 20:46, Stefan Hajnoczi wrote:The QEMU Project has 50,000 minutes of GitLab CI quota. Let's enable GitLab Merge Requests so that anyone can submit a merge request and get CI coverage.Each merge request consumes about 2500. That won't last long.Yikes, that is 41 hours per CI run. I wonder if GitLab's CI minutes are on slow machines or if we'll hit the same issue with dedicated runners. It seems like CI optimization will be necessary...
Shared runners are 1 vCPU, so it's really 41 CPU hours per CI run. That's a lot but not unheard of.
Almost every 2-socket server these days will have at least 50 CPUs; with some optimization we probably can get it down to half an hour of real time, on a single server running 3-4 runners with 16 vCPUs.
Paolo
[Prev in Thread] | Current Thread | [Next in Thread] |