git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: git-pull from git.git - no remote ref for pu or next?
Date: Tue, 12 Dec 2006 21:04:54 +0100	[thread overview]
Message-ID: <eln1sr$1rm$1@sea.gmane.org> (raw)
In-Reply-To: Pine.LNX.4.64.0612121144220.3535@woody.osdl.org

Linus Torvalds wrote:

> 
> 
> On Tue, 12 Dec 2006, Johannes Schindelin wrote:
>> On Tue, 12 Dec 2006, Nicolas Pitre wrote:
>> 
>>> On Tue, 12 Dec 2006, Johannes Schindelin wrote:
>>> 
>>>> But it would become a non-problem when the HTTP transport would learn 
>>>> to read and interpret the .idx files, basically constructing thin 
>>>> packs from parts of the .pack files ("Content-Range:" comes to 
>>>> mind)...
>>> 
>>> Woooh.
>> 
>> Does that mean "Yes, I'll do it"? ;-)
> 
> Umm. I hope it means "Woooh, that's crazy talk".
> 
> You do realize that then you need to teach the http-walker about walking 
> the delta chain all the way up? For big pulls, you're going to be a lot 
> _slower_ than just downloading the whole dang thing, because the delta 
> objects are often just ~40 bytes, and you've now added a ping-pong latency 
> for each such small transfer.
> 
> You don't need to download many such small ranges, and suddenly the few 
> hundred ping-pongs that got you a few tens of kB of data took longer than 
> just downloading a big stream efficiently that got you everything.

While I think the problem is much better solved by having "archive" pack(s)
and "current" pack, perhaps with always sownloading the whole delta it
would be feasible?

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git


  reply	other threads:[~2006-12-12 20:03 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-12 16:44 git-pull from git.git - no remote ref for pu or next? Randal L. Schwartz
2006-12-12 16:47 ` Randal L. Schwartz
2006-12-12 17:40   ` Johannes Schindelin
2006-12-12 17:42     ` Randal L. Schwartz
2006-12-12 17:56   ` Linus Torvalds
2006-12-12 18:09     ` Johannes Schindelin
2006-12-12 18:23       ` Linus Torvalds
2006-12-12 19:07         ` Nicolas Pitre
2006-12-12 19:13           ` Linus Torvalds
2006-12-12 19:18         ` Jakub Narebski
2006-12-12 18:54       ` Nicolas Pitre
2006-12-12 19:04         ` Johannes Schindelin
2006-12-12 19:15           ` Jakub Narebski
2006-12-12 19:26           ` Nicolas Pitre
2006-12-12 19:32             ` Johannes Schindelin
2006-12-12 19:48               ` Linus Torvalds
2006-12-12 20:04                 ` Jakub Narebski [this message]
2006-12-12 20:26                 ` Johannes Schindelin
2006-12-12 19:50               ` Nicolas Pitre
2006-12-12 18:51     ` Nicolas Pitre
2006-12-12 19:03       ` Linus Torvalds
2006-12-12 21:26     ` 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='eln1sr$1rm$1@sea.gmane.org' \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    /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).