From: Jakub Narebski <jnareb@gmail.com>
To: Mike Hommey <mh@glandium.org>
Cc: Jeff King <peff@peff.net>, git@vger.kernel.org
Subject: Re: Surprising use of memory and time when repacking mozilla's gecko repository
Date: Fri, 05 Jul 2019 13:29:52 +0200 [thread overview]
Message-ID: <86bly81zyn.fsf@gmail.com> (raw)
In-Reply-To: <20190705054736.6llkhnopt2fcta2k@glandium.org> (Mike Hommey's message of "Fri, 5 Jul 2019 14:47:36 +0900")
Mike Hommey <mh@glandium.org> writes:
> On Fri, Jul 05, 2019 at 01:14:13AM -0400, Jeff King wrote:
>> On Thu, Jul 04, 2019 at 10:13:20PM +0900, Mike Hommey wrote:
[...]
>> I think I explained all of the memory-usage questions in my earlier
>> response, but just for reference: if you have access to it, valgrind's
>> "massif" tool is really good for this kind of profiling. Something like:
>>
>> valgrind --tool=massif git pack-objects ...
>> ms_print massif.out.*
>>
>> which shows heap usage at various times, points out the snapshot with
>> peak usage, and shows a backtrace of the main culprits at a few
>> snapshots.
>
> At the expense of time ;) A run would likely last an entire day under
> massif (by which I mean a full 24 hours, not a 9-5 day).
Valgrind, as I understand it, runs the program under emulation. I
wonder if perf / OProfile based solution could help here (gathering
memory-based events and metrics).
There is also trace2 built-in into Git, but I don't know if it could be
used for this purpose or not.
Best,
--
Jakub Narębski
next prev parent reply other threads:[~2019-07-05 11:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-04 10:05 Surprising use of memory and time when repacking mozilla's gecko repository Mike Hommey
2019-07-04 12:04 ` Eric Wong
2019-07-04 13:13 ` Mike Hommey
2019-07-05 5:14 ` Jeff King
2019-07-05 5:47 ` Mike Hommey
2019-07-05 11:29 ` Jakub Narebski [this message]
2019-07-05 0:22 ` Mike Hommey
2019-07-05 4:45 ` Mike Hommey
2019-07-05 5:09 ` Jeff King
2019-07-05 5:45 ` Mike Hommey
2019-07-05 11:51 ` Mike Hommey
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86bly81zyn.fsf@gmail.com \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=mh@glandium.org \
--cc=peff@peff.net \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).