git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: perforce import: git-p4 memory usage

From
Andreas Ericsson <ae@op5.se>
Date
May 23, 2008, 11:25 UTC
Message-ID
<4836A9B8.6070804@op5.se>
In-Reply-To
<H1SlcXmh.1211537268.4996380.lgd@diamand.org>
Luke Diamand wrote:
Show 15 quoted lines
> 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
Previous: Luke DiamandNext: Logan Kennelly
Message 2 of 3 in “perforce import: git-p4 memory usage”
  1. Luke DiamandMay 23, 2008
  2. Andreas EricssonMay 23, 2008
  3. Logan KennellyMay 23, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.