From: David Kastrup <dak@gnu.org>
To: John Keeping <john@keeping.me.uk>
Cc: Duy Nguyen <pclouds@gmail.com>, Git Mailing List <git@vger.kernel.org>
Subject: Re: Profiling support?
Date: Tue, 11 Feb 2014 16:19:55 +0100 [thread overview]
Message-ID: <874n45brs4.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <20140211151451.GA15032@serenity.lan> (John Keeping's message of "Tue, 11 Feb 2014 15:14:52 +0000")
John Keeping <john@keeping.me.uk> writes:
> On Tue, Feb 11, 2014 at 03:41:55PM +0100, David Kastrup wrote:
>> Duy Nguyen <pclouds@gmail.com> writes:
>>
>> > Would perf help? No changes required, and almost no overhead, I think.
>>
>> Not useful. It would be probably nice for nailing down the performance
>> gains when the work is finished so that future regressions will be
>> noticeable. It's reasonable easy to create a test case that will take
>> hours with the current git-blame and would finish in seconds with the
>> improved one.
>>
>> But it's not useful at all for figuring out the hotspots within the
>> git-blame binary.
>
> I would have thought the annotation described at [1] is exactly what
> you're looking for, isn't it?
>
> Alternatively, I've had some success with callgrind and kCachegrind in
> the past.
>
> [1]
> https://perf.wiki.kernel.org/index.php/Tutorial#Source_level_analysis_with_perf_annotate
Misunderstanding on my part. I thought this was about the "make perf"
Makefile target. I'll have to take a look at what the perf utility
does.
Thanks for the clarification.
--
David Kastrup
next prev parent reply other threads:[~2014-02-11 15:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-11 11:17 Profiling support? David Kastrup
2014-02-11 13:18 ` Duy Nguyen
2014-02-11 14:41 ` David Kastrup
2014-02-11 15:14 ` John Keeping
2014-02-11 15:19 ` David Kastrup [this message]
2014-02-11 20:53 ` David Kastrup
2014-02-16 15:44 ` Thomas Rast
2014-02-16 15:59 ` David Kastrup
2014-02-16 16:54 ` Thomas Rast
2014-02-16 17:05 ` David Kastrup
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=874n45brs4.fsf@fencepost.gnu.org \
--to=dak@gnu.org \
--cc=git@vger.kernel.org \
--cc=john@keeping.me.uk \
--cc=pclouds@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.