Re: git blame with valgrind massif

From: Pierre Habouzit <madcoder@debian.org>
Date: Dec 11, 2007, 21:27 UTC
Message-ID: <20071211212743.GD29110@artemis.madism.org>
In-Reply-To: <alpine.LFD.0.9999.0712111315060.25032@woody.linux-foundation.org>

On Tue, Dec 11, 2007 at 09:22:53PM +0000, Linus Torvalds wrote:

Show 16 quoted lines

> 
> 
> On Tue, 11 Dec 2007, Jon Smirl wrote:
> > 
> > How do you interpret the massif output?
> 
> Not very easy, since massif will tell you what *allocated* it, but then 
> trying to see who was supposed to free it is another issue altogether.
> 
> I also find the textual output to be very confusing. But what massif is 
> really good at is to look at the memory usage over time in the postscript 
> file it generates, and that gives you a much better feel for what 
> particular allocation is a problem.
> 
> In this case, it's patch_delta that generates all the memory usage (well, 
> 98% of it ;^), but that's not that helpful unless you know git internals,

  No 37%, the 98% list is the list of calls that generate 98% of the
total allocations git blame does, and then massif lists each individual
call, and patch_delta generates 37% of the total.

  Though it's meaningless without knowing how much time this memory
stayed allocated>

-- 
·O·  Pierre Habouzit
··O                                                madcoder@debian.org
OOO                                                http://www.madism.org