From: Paolo Bonzini <pbonzini@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Thomas Huth" <thuth@redhat.com>,
"Daniel P . Berrange" <berrange@redhat.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
qemu-devel <qemu-devel@nongnu.org>,
"Cleber Rosa" <crosa@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: Serious doubts about Gitlab CI
Date: Fri, 19 Mar 2021 10:41:46 +0100 [thread overview]
Message-ID: <ea7bf28e-c0e2-8350-04be-b7052c2238ee@redhat.com> (raw)
In-Reply-To: <YFRv9zMvBXtpfN3t@stefanha-x1.localdomain>
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
next prev parent reply other threads:[~2021-03-19 9:43 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 20:29 Serious doubts about Gitlab CI Philippe Mathieu-Daudé
2021-03-18 1:28 ` Bin Meng
2021-03-18 8:55 ` Philippe Mathieu-Daudé
2021-03-18 9:33 ` Daniel P. Berrangé
2021-03-18 9:50 ` Philippe Mathieu-Daudé
2021-03-18 10:28 ` Philippe Mathieu-Daudé
2021-03-19 5:34 ` Thomas Huth
2021-03-18 19:46 ` Stefan Hajnoczi
2021-03-18 19:52 ` John Snow
2021-03-18 20:53 ` Philippe Mathieu-Daudé
2021-03-18 20:30 ` Paolo Bonzini
2021-03-19 9:33 ` Stefan Hajnoczi
2021-03-19 9:41 ` Paolo Bonzini [this message]
2021-03-19 11:44 ` Philippe Mathieu-Daudé
2021-03-19 10:18 ` Andrew Jones
2021-03-19 10:59 ` Paolo Bonzini
2021-03-19 11:34 ` Philippe Mathieu-Daudé
2021-03-19 15:27 ` Wainer dos Santos Moschetta
2021-03-29 14:10 ` Stefan Hajnoczi
2021-03-30 11:19 ` Daniel P. Berrangé
2021-03-30 11:55 ` Thomas Huth
2021-03-30 12:09 ` Paolo Bonzini
2021-03-30 12:23 ` Philippe Mathieu-Daudé
2021-03-30 12:45 ` Paolo Bonzini
2021-03-30 13:12 ` Daniel P. Berrangé
2021-03-30 13:19 ` Paolo Bonzini
2021-03-30 13:27 ` Daniel P. Berrangé
2021-03-30 15:59 ` Warner Losh
2021-03-30 16:11 ` Peter Maydell
2021-03-30 16:24 ` Warner Losh
2021-03-30 16:10 ` Thomas Huth
2021-03-30 13:09 ` Daniel P. Berrangé
2021-03-30 12:09 ` Paolo Bonzini
2021-03-30 12:19 ` Peter Maydell
2021-03-30 12:33 ` Philippe Mathieu-Daudé
2021-03-30 13:19 ` Daniel P. Berrangé
2021-03-31 7:54 ` Thomas Huth
2021-03-31 9:31 ` Andrea Bolognani
2021-03-30 14:13 ` Stefan Hajnoczi
2021-03-30 14:23 ` Paolo Bonzini
2021-03-30 14:30 ` Daniel P. Berrangé
2021-03-30 14:09 ` Stefan Hajnoczi
2021-03-19 12:07 ` Markus Armbruster
2021-03-19 13:06 ` Thomas Huth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ea7bf28e-c0e2-8350-04be-b7052c2238ee@redhat.com \
--to=pbonzini@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=crosa@redhat.com \
--cc=f4bug@amsat.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=thuth@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).