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

Re: git-svn init/fetch: wow that's slow

From
Sam Vilain <sam@vilain.net>
Date
Apr 22, 2009, 11:05 UTC
Message-ID
<1240398352.20236.26.camel@maia.lan>
In-Reply-To
<fabb9a1e0904220255w55c8fee1uf534aad07cefa818@mail.gmail.com>
On Wed, 2009-04-22 at 11:55 +0200, Sverre Rabbelier wrote:
Show 11 quoted lines
> Heya,
> 
> On Wed, Apr 22, 2009 at 09:40, Lachlan Deck <lachlan.deck@gmail.com> wrote:
> > Okay, so I'm using git 1.6.2. I assume this is all a 'known issue'. Has
> > there been any work / plans towards improving this?
> 
> This can be improved by using svn 1.5's delta feature, however, Eric
> (the author of git-svn) does not have the time to do this, and no-one
> has stepped up to do this.
> A workaround is to not clone from r1 but instead start at a more
> recent revision.

Fetching over plain svn:// is IME much faster. But let's face it, SVN is no race-horse and was never designed for the case where people like to look at their history much. Developing with a trunk was so painful, people would rather just forget...

One workaround is to use SVK to do the initial mirroring, and the --use-svm-mirror flag to convert your SVK mirror path to git. See http://utsl.gen.nz/talks/git-svn/intro.html for a guide for the second part of that. SVK has implemented some of the harder parts of the SVN API to get right, such as request pipelining - see http://code.bestpractical.com/svk/trunk/lib/SVK/Mirror/Backend/SVNRaPipe.pm for how the SVN API "supports" this. As a result of this dedication to the cause, SVK does this part very quickly.

Sam
Previous: Sverre RabbelierNext: Matthieu Moy
Message 3 of 4 in “git-svn init/fetch: wow that's slow”
  1. Lachlan DeckApr 22, 2009
  2. Sverre RabbelierApr 22, 2009
  3. Sam VilainApr 22, 2009
  4. Matthieu MoyApr 22, 2009

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.