From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Pierre Habouzit" <madcoder@debian.org>,
"Jon Smirl" <jonsmirl@gmail.com>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: git blame with valgrind massif
Date: Tue, 11 Dec 2007 16:45:48 -0500 [thread overview]
Message-ID: <9e4733910712111345i23d86a85jfedb4f37f20a5b0@mail.gmail.com> (raw)
In-Reply-To: <20071211212052.GC29110@artemis.madism.org>
On 12/11/07, Pierre Habouzit <madcoder@debian.org> wrote:
> On Tue, Dec 11, 2007 at 08:57:24PM +0000, Jon Smirl wrote:
> > I ran:
> > valgrind --tool=massif --heap=yes git blame gcc/ChangeLog
> > it used about 2.25GB
> >
> > How do you interpret the massif output?
>
> would you mind putting the postscript it generated somewhere too ?
> it's usually pretty informative, because the amount of data allocated is
> not all, its liveness is an important information too.
It was very boring. A diagonal line from 0 to 2GB.
>
> --
> ·O· Pierre Habouzit
> ··O madcoder@debian.org
> OOO http://www.madism.org
>
>
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2007-12-11 21:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-11 20:57 git blame with valgrind massif Jon Smirl
2007-12-11 21:20 ` Pierre Habouzit
2007-12-11 21:45 ` Jon Smirl [this message]
2007-12-12 0:50 ` André Goddard Rosa
2007-12-11 21:22 ` Linus Torvalds
2007-12-11 21:27 ` Pierre Habouzit
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=9e4733910712111345i23d86a85jfedb4f37f20a5b0@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=git@vger.kernel.org \
--cc=madcoder@debian.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).