From: Patrick Steinhardt <ps@pks.im>
To: Tamir Duberstein <tamird@gmail.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
Jeff King <peff@peff.net>
Subject: Re: [PATCH v2 2/2] ci: align job counts across CI providers
Date: Mon, 28 Sep 2026 13:14:47 +0200 [thread overview]
Message-ID: <arpMJ4EBomeSF6LS@pks.im> (raw)
In-Reply-To: <CAJ-ks9mWU2cFWLfioSSM_6Ct1ydtxn3i4Dh-L537M5EDiMW3vQ@mail.gmail.com>
On Mon, Sep 28, 2026 at 06:16:33AM -0400, Tamir Duberstein wrote:
> On Mon, Sep 28, 2026 at 2:36 AM Patrick Steinhardt <ps@pks.im> wrote:
> >
> > On Fri, Sep 25, 2026 at 12:35:39PM -0400, Tamir Duberstein wrote:
> > > GitHub Actions sets JOBS to ten regardless of runner size, while
> > > GitLab CI uses the detected CPU count. Use the CPU count for Make and
> > > prove on both providers, selecting JOBS after the operating system
> > > is identified.
> >
> > Again, it should be noted here what the effect of this is. In other
> > words, does GitHub slow down as a result? You already showed numbers
> > during the discussion on v1 of this series, and these numbers should
> > probably be included in this message, too.
>
> Agreed, but in this case there was no reliable performance change
> across 10 runs; I could include that.
I think it should be included, as it's the one thing that people will be
wondering about when they see this change.
Patrick
next prev parent reply other threads:[~2026-09-28 11:14 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 17:13 [PATCH 0/2] ci: reduce pressure from large test fixtures Tamir Duberstein
2026-09-23 17:13 ` [PATCH 1/2] t4205: compare huge output without diff Tamir Duberstein
2026-09-24 6:13 ` Patrick Steinhardt
2026-09-24 20:41 ` Tamir Duberstein
2026-09-25 0:13 ` Jeff King
2026-09-25 6:41 ` Junio C Hamano
2026-09-28 6:36 ` Patrick Steinhardt
2026-09-23 17:13 ` [PATCH 2/2] ci: match Linux jobs to available CPUs Tamir Duberstein
2026-09-24 6:13 ` Patrick Steinhardt
2026-09-25 15:03 ` Tamir Duberstein
2026-09-23 18:36 ` [PATCH 0/2] ci: reduce pressure from large test fixtures Tamir Duberstein
2026-09-25 16:35 ` [PATCH v2 0/2] ci: use cmp and align job-count selection Tamir Duberstein
2026-09-25 16:35 ` [PATCH v2 1/2] t4205: compare huge output without diff Tamir Duberstein
2026-09-28 6:36 ` Patrick Steinhardt
2026-09-25 16:35 ` [PATCH v2 2/2] ci: align job counts across CI providers Tamir Duberstein
2026-09-28 6:36 ` Patrick Steinhardt
2026-09-28 10:16 ` Tamir Duberstein
2026-09-28 11:14 ` Patrick Steinhardt [this message]
2026-09-30 14:20 ` [PATCH v3 0/2] ci: use cmp and align job-count selection Tamir Duberstein
2026-09-30 14:20 ` [PATCH v3 1/2] t4205: compare huge output without diff Tamir Duberstein
2026-09-30 14:20 ` [PATCH v3 2/2] ci: use twice the CPU count on both providers Tamir Duberstein
2026-09-30 14:45 ` Patrick Steinhardt
2026-09-30 14:45 ` [PATCH v3 0/2] ci: use cmp and align job-count selection Patrick Steinhardt
2026-09-30 14:58 ` Tamir Duberstein
2026-09-30 18:04 ` Junio C Hamano
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=arpMJ4EBomeSF6LS@pks.im \
--to=ps@pks.im \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=tamird@gmail.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.