From: Luke Diamand <luke@diamand.org>
To: Corey Thompson <cmtptr@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git-p4 out of memory for very large repository
Date: Fri, 23 Aug 2013 20:42:44 +0100 [thread overview]
Message-ID: <5217BB34.9080502@diamand.org> (raw)
In-Reply-To: <20130823115920.GB8182@jerec>
I think I've cloned files as large as that or larger. If you just want to
clone this and move on, perhaps you just need a bit more memory? What's the
size of your physical memory and swap partition? Per process memory limit?
On 23 Aug 2013 12:59, "Corey Thompson" <cmtptr@gmail.com> wrote:
On 23/08/13 12:59, Corey Thompson wrote:
> On Fri, Aug 23, 2013 at 07:48:56AM -0400, Corey Thompson wrote:
>> Sorry, I guess I could have included more details in my original post.
>> Since then, I have also made an attempt to clone another (slightly more
>> recent) branch, and at last had success. So I see this does indeed
>> work, it just seems to be very unhappy with one particular branch.
>>
>> So, here are a few statistics I collected on the two branches.
>>
>> branch-that-fails:
>> total workspace disk usage (current head): 12GB
>> 68 files over 20MB
>> largest three being about 118MB
>>
>> branch-that-clones:
>> total workspace disk usage (current head): 11GB
>> 22 files over 20MB
>> largest three being about 80MB
>>
>> I suspect that part of the problem here might be that my company likes
>> to submit very large binaries into our repo (.tar.gzs, pre-compiled
>> third party binaries, etc.).
>>
>> Is there any way I can clone this in pieces? The best I've come up with
>> is to clone only up to a change number just before it tends to fail, and
>> then rebase to the latest. My clone succeeded, but the rebase still
>> runs out of memory. It would be great if I could specify a change
>> number to rebase up to, so that I can just take this thing a few hundred
>> changes at a time.
>>
>> Thanks,
>> Corey
>
> And I still haven't told you anything about my platform or git
> version...
>
> This is on Fedora Core 11, with git 1.8.3.4 built from the github repo
> (117eea7e).
next prev parent reply other threads:[~2013-08-23 19:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-23 1:12 git-p4 out of memory for very large repository Corey Thompson
2013-08-23 7:16 ` Luke Diamand
2013-08-23 11:48 ` Corey Thompson
2013-08-23 11:59 ` Corey Thompson
2013-08-23 19:42 ` Luke Diamand [this message]
2013-08-24 0:56 ` Corey Thompson
2013-08-25 15:50 ` Pete Wyckoff
2013-08-26 13:47 ` Corey Thompson
2013-08-28 15:41 ` Corey Thompson
2013-08-29 22:46 ` Pete Wyckoff
2013-09-02 19:42 ` Luke Diamand
2013-09-06 19:03 ` Corey Thompson
2013-09-07 8:19 ` Pete Wyckoff
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=5217BB34.9080502@diamand.org \
--to=luke@diamand.org \
--cc=cmtptr@gmail.com \
--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).