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

Re: git-svn: why fetching files is so slow

From
Junio C Hamano <junkio@cox.net>
Date
Nov 24, 2006, 20:42 UTC
Message-ID
<7vy7q0a85p.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<20061124203320.GA21654@soma>
Eric Wong <normalperson@yhbt.net> writes:
Show 12 quoted lines
> 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"?

Previous: Eric WongNext: Eric Wong
Message 6 of 8 in “git-svn: why fetching files is so slow”
  1. PazuNov 24, 2006
  2. Seth FalconNov 24, 2006
  3. Eric WongNov 24, 2006
  4. PazuNov 24, 2006
  5. Eric WongNov 24, 2006
  6. Junio C HamanoNov 24, 2006
  7. Eric WongNov 24, 2006
  8. 2/2 git-svn: update tests for recent changesEric Wong, Nov 28, 2006

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.