Re: git-svn: why fetching files is so slow
- From
- Eric Wong <normalperson@yhbt.net>
- Date
- Nov 24, 2006, 22:14 UTC
- Message-ID
- <20061124221435.GA21072@localdomain>
- In-Reply-To
- <7vy7q0a85p.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano <junkio@cox.net> wrote:
Show 20 quoted lines
> Eric Wong <normalperson@yhbt.net> writes: > > > Pazu <pazu@pazu.com.br> wrote: > >> Eric Wong <normalperson <at> yhbt.net> writes: > >> > >> > git-svn transfers full files, and not deltas. I'll hopefully have a > >> > chance to look into improving the situation for slow links this weekend. > >> > >> Yes, but why would that make fetching the first revision slower? In this > >> situation, both svn and git-svn would have to fetch full files. Maybe git-svn > >> isn't using gzip compression or http pipelining? > > > > Even for the initial transfer, the tree is bundled into one big delta > > (at least over https). > > Do you mean that "one big delta" saves duplicates across copies > inside the tree (e.g. svn tags and branches can be expressed as > a mostly identical copies of each other), or do you mean "one > full file at a time" requests are killing us, compared to a such > single transfer of "one big delta"?
One full file at a time requests are definitely killing us (over slow links, at least). I'm not sure how/if duplicates inside a requested tree are optimized on the server side.