From: Junio C Hamano <gitster@pobox.com>
Date: Mon, 11 Jun 2012 16:16:49 GMT
Subject: Re: branch --contains is unbearably slow [Re: [PATCHv2] Warnings before rebasing -i published history]
Message-ID: <7vvcix7rim.fsf@alter.siamese.dyndns.org>
In-Reply-To: <87r4tmhy12.fsf_-_@thomas.inf.ethz.ch>

Thomas Rast <trast@student.ethz.ch> writes:

>   $ time git branch -r --contains origin/next
>     origin/next
>
>   real    0m32.060s
>   user    0m31.895s
>   sys     0m0.036s
>
> I think an upper bound for the runtime of any 'git branch --contains'
> should be generating the *complete* topology like this:
>
>   $ time git log --graph --oneline --all >/dev/null
>
>   real    0m2.637s
>   user    0m2.246s
>   sys     0m0.364s

Hrm, there must be something I am doing wrong.

    $ time git log --graph --oneline --all >/dev/null

    real    0m3.896s
    user    0m3.476s
    sys     0m0.416s

Ok, so my disk is slower than yours, perhaps.  But

    $ time git branch -r --contains next
      github2/next
      gph/next
      ko/next
      repo/next

    real    0m3.853s
    user    0m3.804s
    sys     0m0.048s