From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Brian Downing" <bdowning@lavos.net>
Cc: "Git Mailing List" <git@vger.kernel.org>
Subject: Re: Reducing the memory footprint
Date: Fri, 9 Nov 2007 20:05:30 -0500 [thread overview]
Message-ID: <9e4733910711091705i6f77d05uc5ba04f668796a73@mail.gmail.com> (raw)
In-Reply-To: <20071110005327.GH6212@lavos.net>
On 11/9/07, Brian Downing <bdowning@lavos.net> wrote:
> On Fri, Nov 09, 2007 at 06:38:00PM -0500, Jon Smirl wrote:
> > I'm using this config file:
> >
> > [pack]
> > windowMemory = 1M
> > deltaCacheSize = 1M
> >
> > And I have NO_MMAP compiled in.
> >
> > git is still using over 200MB of memory or address space, my process
> > gets killed either way.
>
> I'm assuming it's dying on repacking since you included the pack
> parameters.
>
> How big is your biggest object? Even with pack.windowMemory, it still
> keeps the last object around to try and delta against (in other words,
> the window only shrinks to size 1), which means you have to have room
> for it and its delta index.
It's a Linux kernel repository. Git receive-pack is going over 200MB
and getting zapped. I don't understand why the process is so large. I
am compiled with -DNO_MMAP.
I think I have a achieved a work around. I rsync'd in my last several
weeks of changes. Now I can 'git push' small amounts of changes
without getting killed.
I'm begging dreamhost to simply install git. Installed commands don't
get zapped.
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2007-11-10 1:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-09 23:38 Reducing the memory footprint Jon Smirl
2007-11-10 0:53 ` Brian Downing
2007-11-10 1:05 ` Jon Smirl [this message]
2007-11-10 6:07 ` Jon Smirl
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=9e4733910711091705i6f77d05uc5ba04f668796a73@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=bdowning@lavos.net \
--cc=git@vger.kernel.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).