All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: Thomas Huth <thuth@redhat.com>,
	alex.bennee@linaro.org, qemu-devel@nongnu.org
Subject: Re: [PATCH 2/3] ci: do not use #processors+1 jobs, #processors is enough
Date: Tue, 18 May 2021 14:48:39 +0200	[thread overview]
Message-ID: <885e30da-8d6d-7d58-7733-f66477633e65@redhat.com> (raw)
In-Reply-To: <YKO2ZbDsphiXh/pE@redhat.com>

On 18/05/21 14:43, Daniel P. Berrangé wrote:
> I'd be surprised if you can measure any statistically reliable difference
> at all wrt public CI. I've tried measuring CI performance for small changes
> and found it impossible in short time frames, as the deviation between runs
> is way too large. GitLab CI speeds tend to slow down as the day goes on and
> US wakes up, so by time you run QEMU CI a second time in the day, it will
> be slower. They clearly overcommit resources on the cloud host so you're
> at the mercy of whatever else is running.

Yeah, I was going to test it locally (using CPU offlining and hugetlbfs 
to simulate a 4-CPU machine with not that much memory).

Paolo



  reply	other threads:[~2021-05-18 12:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-18  8:41 [PATCH 0/3] Small CI improvements Paolo Bonzini
2021-05-18  8:41 ` [PATCH 1/3] cirrus-ci: test installation Paolo Bonzini
2021-05-18 13:50   ` Alex Bennée
2021-05-19 14:44     ` Paolo Bonzini
2021-05-18  8:41 ` [PATCH 2/3] ci: do not use #processors+1 jobs, #processors is enough Paolo Bonzini
2021-05-18  8:56   ` Philippe Mathieu-Daudé
2021-05-18 10:49   ` Thomas Huth
2021-05-18 12:30     ` Paolo Bonzini
2021-05-18 12:43       ` Daniel P. Berrangé
2021-05-18 12:48         ` Paolo Bonzini [this message]
2021-05-18  8:41 ` [PATCH 3/3] ci: add -j to all "make" jobs Paolo Bonzini
2021-05-18  8:58   ` Philippe Mathieu-Daudé
2021-05-19 15:28 ` [PATCH 0/3] Small CI improvements Alex Bennée

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=885e30da-8d6d-7d58-7733-f66477633e65@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=berrange@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.