git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Wong <normalperson@yhbt.net>
To: Steven Grimm <koreth@midwinter.com>
Cc: Geert Bosch <bosch@adacore.com>,
	"git@vger.kernel.org List" <git@vger.kernel.org>
Subject: Re: Excruciatingly slow git-svn imports
Date: Tue, 29 Apr 2008 00:11:22 -0700	[thread overview]
Message-ID: <20080429071122.GG24171@muzzle> (raw)
In-Reply-To: <2C39C19D-0B81-4879-92DC-C0436DB6E84E@midwinter.com>

Steven Grimm <koreth@midwinter.com> wrote:
> On Apr 24, 2008, at 11:54 AM, Geert Bosch wrote:
> 
> >I'm trying to import a 9.7G, 130K revision svn repository
> >but it seems to only import about 6K revisions per day on fast  
> >hardware
> >using a recent git (1.5.5).
> 
> I've found that git-svn gets slower as it runs. Try interrupting the  
> clone and running "git svn fetch" -- it should pick up where it left  
> off and will be MUCH faster if my experience is any indication. When I  
> clone the big svn repository at work I usually restart it every 1000  
> revisions or so and it finishes in a fraction of the time it takes if  
> I let it do everything in a single run.

That's really strange to hear...  The git-svn process itself does not
store much state other than the current revision and the log information
for the next 100 or so revisions it needs to import.

Are you packing the repository?  Which SVN protocol are you using?  Does
memory usage of git-svn stay stable throughout the run?

-- 
Eric Wong

  reply	other threads:[~2008-04-29  7:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-24 18:54 Excruciatingly slow git-svn imports Geert Bosch
2008-04-24 19:57 ` Steven Grimm
2008-04-29  7:11   ` Eric Wong [this message]
2008-05-05  4:29     ` Geert Bosch
2008-05-06  3:28       ` Eric Wong
2008-05-06  3:56         ` Avery Pennarun
2008-05-06  4:25           ` Eric Wong
2008-05-06 11:23             ` Geert Bosch
2008-04-29  7:03 ` Eric Wong

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=20080429071122.GG24171@muzzle \
    --to=normalperson@yhbt.net \
    --cc=bosch@adacore.com \
    --cc=git@vger.kernel.org \
    --cc=koreth@midwinter.com \
    /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).