On Mon, Aug 11, 2008 at 7:47 AM, Ken Pratt <ken@xxxxxxxxxxxx> wrote: > A "git repack -a -d" only takes 5 seconds to run on the same > repository on my laptop (a non-bare copy), and seems to peak at ~160MB > of RAM usage. As a workaround, if you repack on your laptop and rsync the pack+index to the server, it will work. This can be used to serve huge projects out of lightweight-ish servers. Yet another workaround is to perform initial clones via rsync or http. In your case, I agree that the repo doesn't seem large enough (or to have large enough objects) to warrant having this problem. But that I can't help much with myself - pack-machiner experts probably can. cheers, m -- martin.langhoff@xxxxxxxxx martin@xxxxxxxxxx -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff -- To unsubscribe from this list: 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
