From: Matthieu Moy <Matthieu.Moy@imag.fr>
To: "Karl Hasselström" <kha@treskal.com>
Cc: A B <gentosaker@gmail.com>, git@vger.kernel.org
Subject: Re: git bisect on multiple cores
Date: Wed, 09 Apr 2008 10:07:25 +0200 [thread overview]
Message-ID: <vpq63ure9j6.fsf@bauges.imag.fr> (raw)
In-Reply-To: <20080409071750.GA23211@diana.vm.bytemark.co.uk> ("Karl Hasselström"'s message of "Wed\, 9 Apr 2008 09\:17\:50 +0200")
Karl Hasselström <kha@treskal.com> writes:
> On 2008-04-08 12:58:47 +0200, A B wrote:
>
>> git bisect is really cool. I use it for the first time. Just a
>> thought, if you have a multiple core computer, can't you make git
>> build new versions in the background while testing the previuos
>> version? Alright, if you build 2 versions, one of them will never be
>> tested, but you will perhaps save some time by letting it build in
>> the background?
>
> Adding parallelism to a binary search scales very badly -- I'd say
> about logarithmically, but I haven't thought hard about it. If it's
> possible to use the extra cores to speed up the build+test cycle,
> that's vastly preferable.
Probably logarithmically with the number of cores. But for reasonable
machines, this number is relatively low, so the log is not so costly.
For a binary search, using just 2 cores, you can try the next in the
list in case of a "git bisect good" for example, and if the hypothesis
is true, you've just gained a factor 2 (assuming it happens 50% of
times, that should be a 50% speedup). Similarly, you should get a
factor 2 with 3 cores.
And as said before, you can also try trisection or N-section. But no,
I won't claim this is simple to implement ;-).
--
Matthieu
next prev parent reply other threads:[~2008-04-09 8:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-08 10:58 git bisect on multiple cores A B
2008-04-08 12:50 ` David Symonds
2008-04-08 18:50 ` Junio C Hamano
2008-04-09 4:29 ` Christian Couder
2008-04-09 5:47 ` Christian Couder
2008-04-09 7:17 ` Karl Hasselström
2008-04-09 8:07 ` Matthieu Moy [this message]
2008-04-09 8:27 ` Karl Hasselström
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=vpq63ure9j6.fsf@bauges.imag.fr \
--to=matthieu.moy@imag.fr \
--cc=gentosaker@gmail.com \
--cc=git@vger.kernel.org \
--cc=kha@treskal.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