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 08:16:58 +0100 [thread overview]
Message-ID: <52170C6A.4080708@diamand.org> (raw)
In-Reply-To: <20130823011245.GA7693@jerec>
On 23/08/13 02:12, Corey Thompson wrote:
> Hello,
>
> Has anyone actually gotten git-p4 to clone a large Perforce repository?
Yes. I've cloned repos with a couple of Gig of files.
> I have one codebase in particular that gets to about 67%, then
> consistently gets get-fast-import (and often times a few other
> processes) killed by the OOM killer.
What size is this codebase? Which version and platform of git are you using?
Maybe it's a regression, or perhaps you've hit some new, previously
unknown size limit?
Thanks
Luke
>
> I've found some patches out there that claim to resolve this, but
> they're all for versions of git-p4.py from several years ago. Not only
> will they not apply cleanly, but as far as I can tell the issues that
> these patches are meant to address aren't in the current version,
> anyway.
>
> Any suggestions would be greatly appreciated.
>
> Thanks,
> Corey
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-08-23 7:17 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 [this message]
2013-08-23 11:48 ` Corey Thompson
2013-08-23 11:59 ` Corey Thompson
2013-08-23 19:42 ` Luke Diamand
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=52170C6A.4080708@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).