From: Han-Wen Nienhuys <hanwen@xs4all.nl>
To: git@vger.kernel.org
Cc: Benjamin Sergeant <bsergean@gmail.com>
Subject: Re: git-p4 fails when cloning a p4 depo.
Date: Mon, 11 Jun 2007 22:08:11 -0300 [thread overview]
Message-ID: <466DF1FB.6010001@xs4all.nl> (raw)
In-Reply-To: <200706090038.33799.simon@lst.de>
Simon Hausmann escreveu:
> On Friday 08 June 2007 20:13:55 Benjamin Sergeant wrote:
>> A perforce command with all the files in the repo is generated to get
>> all the file content.
>> Here is a patch to break it into multiple successive perforce command
>> who uses 4K of parameter max, and collect the output for later.
>>
>> It works, but not for big depos, because the whole perforce depo
>> content is stored in memory in P4Sync.run(), and it looks like mine is
>> bigger than 2 Gigs, so I had to kill the process.
>
> I'd be generally fine with splitting up the "p4 print ..." calls into chunks
> but you have a good point with the memory usage. The old approach of calling
> print per file did not have any of those limitations. Han-Wen, what do you
> think? How much of a performance improvement is the batched print?
One unscientific measurement (getting 1 file vs. 30 files)
indicates that this is about 5x times faster.
--
Han-Wen Nienhuys - hanwen@xs4all.nl - http://www.xs4all.nl/~hanwen
next prev parent reply other threads:[~2007-06-12 1:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-08 16:41 git-p4 fails when cloning a p4 depo Benjamin Sergeant
2007-06-08 18:13 ` Benjamin Sergeant
2007-06-08 21:31 ` Scott Lamb
2007-06-08 21:34 ` Scott Lamb
2007-06-08 22:04 ` Benjamin Sergeant
2007-06-08 22:25 ` Benjamin Sergeant
2007-06-08 23:33 ` Han-Wen Nienhuys
2007-06-09 0:32 ` Benjamin Sergeant
2007-06-08 22:38 ` Simon Hausmann
2007-06-12 1:07 ` Han-Wen Nienhuys
2007-06-12 1:08 ` Han-Wen Nienhuys [this message]
2007-06-12 1:13 ` Han-Wen Nienhuys
2007-06-17 8:11 ` Simon Hausmann
2007-06-17 16:09 ` Benjamin Sergeant
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=466DF1FB.6010001@xs4all.nl \
--to=hanwen@xs4all.nl \
--cc=bsergean@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).