Re: Drastic jump in the time required for the test suite

From: Stefan Beller <sbeller@google.com>
Date: Oct 20, 2016, 16:30 UTC
Message-ID: <CAGZ79ka_McRkOyKH3diCXJSdCm+4pNZfqAqJW_tQLFdhb26tRQ@mail.gmail.com>
In-Reply-To: <20161020123111.qnbsainul2g54z4z@sigill.intra.peff.net>

On Thu, Oct 20, 2016 at 5:31 AM, Jeff King <peff@peff.net> wrote:

Show 13 quoted lines

>
> $ perl -lne '/execve\("(.*?)"/ and print $1' /tmp/foo.out | sort | uniq -c | sort -rn | head
>  152271 /home/peff/compile/git/git
>   57340 /home/peff/compile/git/t/../bin-wrappers/git
>   16865 /bin/sed
>   12650 /bin/rm
>   11257 /bin/cat
>    9326 /home/peff/compile/git/git-sh-i18n--envsubst
>    9079 /usr/bin/diff
>    8013 /usr/bin/wc
>    5924 /bin/mv
>    4566 /bin/grep
>

I am not an expert on perl nor tracing, but is it feasible to find out how many internal calls there are? i.e. either some shell script (rebase, submodule) calling git itself a couple of times or even from compile/git/git itself, e.g. some submodule operations use forking in there.