Re: Excruciatingly slow git-svn imports

From: Avery Pennarun <apenwarr@gmail.com>
Date: May 6, 2008, 03:56 UTC
Message-ID: <32541b130805052056g450b69cfg46693bc3c0c5a1ed@mail.gmail.com>
In-Reply-To: <20080506032846.GA15521@untitled>

On 5/5/08, Eric Wong <normalperson@yhbt.net> wrote:

Show 9 quoted lines

> Interesting.  By  "These commits seemed all to have thousands of files",
>  you mean the first 35K that took up most of the time?  If so, yes,
>  that's definitely a problem...
>
>  git-svn requests a log from SVN containing a list of all paths modified
>  in each revision.  By default, git-svn only requests log entries for up
>  to 100 revisions at a time to reduce memory usage.  However, having
>  thousands of files modified for each revision would still be
>  problematic, as would having insanely long commit messages.

On my system, any branch that was created using "svn cp" of a toplevel directory seems to cause git-svn to (rather slowly) download every single file in the entire branch for the first commit on that branch, giving a symptom that sounds a lot like the above "commits with thousands of files". I assumed this was just an intentional design decision in git-svn, to be slow and safe instead of fast and loose. Is it actually supposed to do something smarter than that?

Thanks,

Avery