bzr and perforce

[Josh Matthews]

Well, I decided to abandon my stress test and tried bzrp4 on a smaller, yet
still substantial subset of the repo.  In this case I sent the output of
p4-fast-export into bzr fast-import, and it looks like as soon as
p4-fast-export was finished, bzr began hogging all the available memory and
the system slowed to a crawl.  However, this passed, and I was left with an
imported repo and 45000 merges to process.  I'll get back to you on the
selftest failures.

Cheers,
Josh

On Mon, Nov 17, 2008 at 5:58 PM, Matt McClure <mlm at aya.yale.edu> wrote:

> Josh,
>
> Thanks for giving it a shot.
>
> On Mon, Nov 17, 2008 at 4:45 PM, Josh Matthews <josh at joshmatthews.net>
> wrote:
> > I nabbed the bzr-p4 trunk, made sure I had p4 and p4d in my path,
> installed
> > P4Python (you should mention that in the docs, by the way) and the p4
> api,
> > ran setup_evn.sh, and ran the selftests.
>
> P4Python is mentioned in the README.  Does P4Python require the P4 C
> API?  If so, yes I should add that to the doc.
>
> > I got at least three failures, and
> > quite possibly more, but there was a metric crapload of information
> > streaming in front of me, so I have no idea what was actually happening.
>
> What were the three failures you can find in the selftest output?
>
> BTW, I inherited that metric crapload of information.  I also would
> like to reduce the amount of logging to the console.
>
> > I'm now stress-testing p4-fast-export against the project I'm working on,
> > which is upwards of 10 million LOC and probably ~10,000 files.  So far my
> > computer's become very unresponsive :)
>
> Where are you sending p4-fast-export's output?  What process is
> consuming your resources, p4-fast-export's Python process?
>
> Matt
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/bazaar/attachments/20081117/65712656/attachment-0001.htm