Re: [RFC] Design for http-pull on repo with packs

2005-07-12 Thread Dan Holmsand
Junio C Hamano wrote: Dan Holmsand [EMAIL PROTECTED] writes: Repacking all of that to a single pack file gives, somewhat surprisingly, a pack size of 62M (+ 1.3M index). In other words, the cost of getting all those branches, and all of the new stuff from Linus, turns out to be *negative*

Re: [RFC] Design for http-pull on repo with packs

2005-07-11 Thread Tony Luck
The big problem, however, comes when Jeff (or anyone else) decides to repack. Then, if you fetch both his repo and Linus', you might end up with several really big pack files, that mostly overlap. That could easily mean storing most objects many times, if you don't do some smart selective

Re: [RFC] Design for http-pull on repo with packs

2005-07-11 Thread Junio C Hamano
Dan Holmsand [EMAIL PROTECTED] writes: I did a little experiment. I cloned Linus' current tree, and git repacked everything (that's 63M + 3.3M worth of pack files). Then I got something like 25 or so of Jeff's branches. That's 6.9M of object files, and 1.4M packed. Total size: 70M for the

Re: [RFC] Design for http-pull on repo with packs

2005-07-10 Thread Dan Holmsand
Daniel Barkalow wrote: I have a design for using http-pull on a packed repository, and it only requires one extra file in the repository: an append-only list of the pack files (because getting the directory listing is very painful and failure-prone). A few comments (as I've been tinkering with

Re: [RFC] Design for http-pull on repo with packs

2005-07-10 Thread Daniel Barkalow
On Sun, 10 Jul 2005, Dan Holmsand wrote: Daniel Barkalow wrote: I have a design for using http-pull on a packed repository, and it only requires one extra file in the repository: an append-only list of the pack files (because getting the directory listing is very painful and

Re: [RFC] Design for http-pull on repo with packs

2005-07-10 Thread Dan Holmsand
Daniel Barkalow wrote: On Sun, 10 Jul 2005, Dan Holmsand wrote: Daniel Barkalow wrote: If an individual file is not available, figure out what packs are available: Get the list of pack files the repository has (currently, I just use e3117bbaf6a59cb53c3f6f0d9b17b9433f0e4135) For any

Re: [RFC] Design for http-pull on repo with packs

2005-07-10 Thread Junio C Hamano
One very minor problem I have with Holmsand approach [*1*] is that the original Barkalow puller allowed a really dumb http server by not requiring directory index at all. For somebody like me with a cheap ISP account [*2*], it was great that I did not have to update 256 index.html files for