John Keeping <j...@keeping.me.uk> writes:
> On Tue, Feb 11, 2014 at 03:41:55PM +0100, David Kastrup wrote:
>> Duy Nguyen <pclo...@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  is exactly what
> you're looking for, isn't it?
> Alternatively, I've had some success with callgrind and kCachegrind in
> the past.
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
Thanks for the clarification.
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html