From: Andreas Ericsson <ae@op5.se>
To: Luke Diamand <luke@diamand.org>
Cc: git@vger.kernel.org
Subject: Re: perforce import: git-p4 memory usage
Date: Fri, 23 May 2008 13:25:44 +0200 [thread overview]
Message-ID: <4836A9B8.6070804@op5.se> (raw)
In-Reply-To: <H1SlcXmh.1211537268.4996380.lgd@diamand.org>
Luke Diamand wrote:
> Hi!
>
> I'm trying to import part of a perforce repo with git-p4.
>
> However, git-p4 appears to try to read all the repo into memory (and
> moreover seems to need about twice as much memory as repo).
>
> Once it runs out of swap, it dies (unsurprisingly).
>
> I think it's failing in readP4Files(), where it appears to read the
> entire repository in one go with "p4 -G -x - print".
>
> Can I just rework this function to do stuff one file at a time? Or is
> that dumb?
>
It's probably a lot slower, and since git works with changesets it
probably won't work all that good unless you somehow construct some
middle-stage which you can then feed to git-fastimport or some such.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
next prev parent reply other threads:[~2008-05-23 11:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-22 15:21 How can I figure out what commits relate to a given diff? Steven A. Falco
2008-05-22 15:48 ` Miklos Vajna
2008-05-22 20:53 ` Steven A. Falco
2008-05-22 16:04 ` Jeff King
2008-05-23 10:07 ` perforce import: git-p4 memory usage, perforce import: git-p4 memory usage Luke Diamand
2008-05-23 11:25 ` Andreas Ericsson [this message]
2008-05-23 22:27 ` Logan Kennelly
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=4836A9B8.6070804@op5.se \
--to=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=luke@diamand.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.