From: Eric Wong <normalperson@yhbt.net>
To: Victor Leschuk <vleschuk@accesssoftek.com>
Cc: Junio C Hamano <gitster@pobox.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [PATCH] git-svn: make batch mode optional for git-cat-file
Date: Wed, 23 Sep 2015 00:35:16 +0000 [thread overview]
Message-ID: <20150923003516.GA6086@dcvr.yhbt.net> (raw)
In-Reply-To: <20150923001350.GA22266@dcvr.yhbt.net>
Eric Wong <normalperson@yhbt.net> wrote:
> Victor Leschuk <vleschuk@accesssoftek.com> wrote:
> > The thing is that git-cat-file keeps growing during work when running
> > in "batch" mode. See the figure attached: it is for cloning a rather
> > small repo (1 hour to clone about ~14000 revisions). However the clone
> > of a large repo (~280000 revisions) took about 2 weeks and
> > git-cat-file has outgrown the parent perl process several times
> > (git-cat-file - ~3-4Gb, perl - 400Mb).
How much of that is anonymous memory, though?
(pmap $PID_OF_GIT_CAT_FILE)
Running the following on the Linux kernel tree I had lying around:
(for i in $(seq 100 200); do git ls-files | sed -e "s/^/HEAD~$i:/"; done)|\
git cat-file --batch >/dev/null
Reveals about 510M RSS in top, but pmap says less than 20M of that
is anonymous. So the rest are mmap-ed packfiles; that RSS gets
transparently released back to the kernel under memory pressure.
next prev parent reply other threads:[~2015-09-23 0:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-21 13:51 [PATCH] git-svn: make batch mode optional for git-cat-file Victor Leschuk
2015-09-21 18:25 ` Junio C Hamano
2015-09-21 22:03 ` Victor Leschuk
2015-09-22 10:47 ` Victor Leschuk
2015-09-22 14:17 ` Junio C Hamano
2015-09-23 0:13 ` Eric Wong
2015-09-23 0:35 ` Eric Wong [this message]
2015-09-23 15:28 ` Victor Leschuk
2015-09-23 19:22 ` Eric Wong
2015-10-11 12:31 ` Victor Leschuk
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=20150923003516.GA6086@dcvr.yhbt.net \
--to=normalperson@yhbt.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=vleschuk@accesssoftek.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 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).