running out of memory when doing a clone of a large repository?

["Paul E. Rybski" <prybski@cs.cmu.edu>]

Hi,
	I've recently started evaluating git for use on one of my projects.  I
used git-svn to convert a fairly large subversion repository and one of
its branches into two separate git repositories following the
instructions found here:

http://www.simplisticcomplexity.com/2008/03/05/cleanly-migrate-your-subversion-repository-to-a-git-repository/

>From that, I created a 1.5G repository from the trunk of the subversion
repo and a 1.1G repository from one of the branches.  I then tried to
clone the repositories from one machine to another via ssh and the
smaller 1.1G repository of the subversion branch (with 1932 commits)
came over just fine but the larger 1.5G repository of the subversion
trunk (5865 commits) died with the following error:

remote: Counting objects: 48415, done.
remote: warning: suboptimal pack - out of memory
error: git-upload-pack: git-pack-objects died with error.
fatal: git-upload-pack: aborting due to possible repository corruption
on the remote side.
remote: aborting due to possible repository corruption on the remote side.
fatal: early EOF
fatal: index-pack failed

Is this simply because the git repository is too large for the machine
that's trying to send it over ssh?  Is there a way to restrict the
memory usage of git or do I need to get more RAM or somehow not import
the full subversion history of my original trunk?

I'm using Ubuntu 8.04.1 on both machines and using the Ubuntu packages
of git version 1.5.4.3.  The machine holding the repository is a 5-year
old AthlonXP 3200 with 1G RAM and 32-bit Ubuntu.  The machine I'm
cloning the repository on is a more recent Intel Dual Core Quad Q6600
with 4GRAM and 64-bit Ubuntu.

Any advice would be greatly appreciated.

Thanks!

-Paul

-- 
Paul E. Rybski, Ph.D., Systems Scientist
The Robotics Institute, Carnegie Mellon University
Phone: 412-268-7417, Fax: 412-268-7350
Web: http://www.cs.cmu.edu/~prybski