Re: Resumable clone/Gittorrent (again)
- From
Nguyen Thai Ngoc Duy <pclouds@gmail.com>
- Date
- Jan 9, 2011, 03:34 UTC
- Message-ID
- <AANLkTi=KPVMEviQhyJeWHynPa2q6NJpQ2VyAhbRcmQ1D@mail.gmail.com>
- In-Reply-To
- <AANLkTim2A4=y=XcuPuPiYGDGZyKAUEk-yv2cZVEGhQ3C@mail.gmail.com>
On Sun, Jan 9, 2011 at 12:21 AM, Luke Kenneth Casson Leighton <luke.leighton@gmail.com> wrote:
> ok - you haven't answered the question: are the chains perfectly > fixed identical sizes?
No.
Show 5 quoted lines
> if so they can be slotted into the bittorrent protocol by simply > pre-selecting the size to match. with the downside that if there are > a million such "chains" you now pretty much overwhelm the peers with > the amount of processing, network traffic and memory requirements to > maintain the "pieces" map.
No, there are thousands of them only (less than 100k for repos I examined). It's precisely the reason I stay away from commits as pieces because commits can potentially go up to millions.
> if not then you now need to modify the bittorrent protocol to cope > with variable-length block sizes: the protocol only allows for the > last block to be of variable-length.
Ah I see. I do not reuse bittorrent code out there. Just its ideas, adapted to git model. If you don't want to modify bittorrent protocol at all, seed a bundle (as mentioned in another thread).
-- Duy