Re: Resumable clone/Gittorrent (again) - stable packs?
- From
Nguyen Thai Ngoc Duy <pclouds@gmail.com>
- Date
- Jan 11, 2011, 01:56 UTC
- Message-ID
- <AANLkTimcmxMxgswrQcqex8b8M717LmTctj=3i7jEHOhZ@mail.gmail.com>
- In-Reply-To
- <4D2BAB0A.1060909@kernel.org>
On Tue, Jan 11, 2011 at 7:57 AM, J.H. <warthog9@kernel.org> wrote:
Show 21 quoted lines
> On 01/10/2011 04:03 PM, Nguyen Thai Ngoc Duy wrote: >> On Mon, Jan 10, 2011 at 11:39 PM, John Wyzer <john.wyzer@gmx.de> wrote: >>> Why not provide an alternative mode for the git:// protocoll that instead of >>> retrieving a big packaged blob breaks this down to the smallest atomic >>> objects from the repository? Those are not changing and should be able to >>> survive partial transfers. >>> While this might not be as efficient network traffic-wise it would provide a >>> solution for those behind breaking connections. >> >> That's what I'm getting to, except that I'll send deltas as much as I can. > > While I think we need to come up with a mechanism to allow for resumable > fetches (I'm thinking slow sporadic links and larger repos like the > kernel for instance), but breaking the repo up into too small a chunks > will very adversely affect the overall transfer and could cause just as > much system thrash on the upstream provider. > > I'd be curious to see what the system impact numbers and performance > differences are though, as I do think getting some sort of resumability > is important, but resumability at the expense of being able to get the > data out quickly and efficiently is not going to be a good trade off :-/
Yeah, I'm interested in those numbers too. Let me get a prototype working, then we'll have numbers to discuss.
-- Duy