git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "D. Ben Knoble" <ben.knoble@gmail.com>
Cc: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>, git@vger.kernel.org
Subject: Re: first bisection step takes quite a while
Date: Thu, 20 Feb 2025 11:17:18 -0800	[thread overview]
Message-ID: <xmqqikp4ctoh.fsf@gitster.g> (raw)
In-Reply-To: <CALnO6CACJTKasKT9rX9w4_r9q0DPOPZhGnHt8f65oo6Q=8NxEg@mail.gmail.com> (D. Ben Knoble's message of "Thu, 20 Feb 2025 13:44:47 -0500")

"D. Ben Knoble" <ben.knoble@gmail.com> writes:

> On Thu, Feb 20, 2025 at 9:38 AM Uwe Kleine-König
> <u.kleine-koenig@baylibre.com> wrote:
>>
>> Hello,
>>
>> today I did a bisection in the kernel repository:
>>
>>         linux$ git version
>>         git version 2.47.1
>>
>>         linux$ time git bisect start 09fbf3d502050282bf47ab3babe1d4ed54dd1fd8 96d8eab5d0a1a9741a4cae1b3c125d75d1aabedf
>>         Bisecting: 572238 revisions left to test after this (roughly 19 steps)
>>         [eafdca4d7010a0e019aaaace3dd71b432a69b54c] Merge tag 'staging-4.18-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging
>>
>>         real    18m41.374s
>>         user    27m18.306s
>>         sys     1m0.565s
>>
>> I was surprised that it took that long to find and checkout the first
>> revision to check. (That is on a 4 x Intel(R) Core(TM) i5-6440HQ CPU @
>> 2.60GHz, 16 GiB RAM with a Samsung SSD. On a different machine (56 x
>> Intel(R) Xeon(R) CPU E5-2660 v4 @ 2.00GHz, 256 GiB RAM and (I think a
>> spinning hard disk)) it took nearly an hour.
>
> Related thread:
> https://lore.kernel.org/git/19461b87a5c.5a2ea74016716.8214238482389812984@zohomail.com/

Indeed.  I haven't had a chance to dig any deeper in the area of the
code since that discussion, but the ideas raised in the messages
near the tail end of the thread may be worth exploring.

THanks for the link.

  reply	other threads:[~2025-02-20 19:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-20 14:35 first bisection step takes quite a while Uwe Kleine-König
2025-02-20 18:44 ` D. Ben Knoble
2025-02-20 19:17   ` Junio C Hamano [this message]
2025-02-21  1:40     ` Junio C Hamano
2025-02-21  9:15       ` Christian Couder
2025-02-21 17:47         ` Junio C Hamano
2025-02-21 20:24           ` Christian Couder
2025-02-21 23:06             ` Christian Couder
2025-02-22  2:15               ` Junio C Hamano
2025-02-24 17:27             ` D. Ben Knoble
2025-02-21  9:28       ` Uwe Kleine-König
2025-02-21 17:29         ` 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=xmqqikp4ctoh.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=ben.knoble@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=u.kleine-koenig@baylibre.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).