On 8/4/06, Linus Torvalds <torvalds@xxxxxxxx> wrote:
and you're basically all done. The above would turn each *,v file into a *-<sha>.pack/*-<sha>.idx file pair, so you'd have exactly as many pack-files as you have *,v files.
I'll end up with 110,000 pack files. I suspect when I run repack over that it is going to take 24hrs or more, but maybe not since everything may be small enough to run in RAM. We'll also get to see the performance of repack with 110K open file handles. How is it going to figure out which file handle contains which objects? A new tool might help. It would concatenate the pack files (while adjusting the headers) and then build a single index. No attempt at searching for deltas. To initially build a single pack file it looks like I need a version of repack that works in a single pass over the input files. To make things simple it would just delete the file when it has finished reading it. Since I'm passing in the revisions in optimal order sorting them probably hurts the pack size. The number of files in flight will be a function of the pipe buffer size and file names. I'll work on the tree writing code over the week end. -- Jon Smirl jonsmirl@xxxxxxxxx - : send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html