Re: git svn's performance on cloning mono's branches/tags...

[Hin-Tak Leung <hintak.leung@gmail.com>]

On Fri, Jun 26, 2009 at 11:57 AM, Andreas Ericsson<ae@op5.se> wrote:
>>> Hin-Tak Leung wrote:
>>>>
>>>> (I'm not on list so please CC)

> Hmm. I've cloned many subversion repositories to git, and I've never
> seen the issues you're seeing. Perhaps because I always cloned the
> entire repository the first time, or because I normally do such things
> over a high-capacity connection, or because I just fire it up and
> forget about it until it's done.

It is not about the capacity/throughput of the connection, but the
latency (round-trip time) of many small transactions - and most of the
unnecessary...

> What happens if you ignore the already-cloned svn tree and just do
> a new import without trying to continue the old one? Not that I'll
> actually do anything about it, as I don't have any problems with it,
> but I'm curious even so ;-)

I did wonder about that - and so I just stopped my branch-tracking
fetch and start all over with svn init -T -t and -b then svn fetch
--all. The first few hundred revisions are very promising: it is
populating the git refs for tag and branch heads
as it goes up.

There are tutorials online about modifying git/config like I did to
adding branches, etc... maybe the example section of git-svn can be
updated with a couple of sentence on 'just throw it away and start
from the beginning if you change your mind from trunk-only to
complex-layout' .

OTOH, I think I would have liked to preserve the compressed object
store, and I think it is possible to graft an object store on an empty
init? The advantage is just that the disc space usage does not widely
fluctuate & no gc steps in the middle.

Thanks for the response anyhow - I just need to remember to blow
trunk-only away and start over next time I change my mind:-).