Thanks for the tips, Martin.

How does git over rsync work? It is unauthenticated, like git over
http? Or authenticated, like git+ssh?

Great ideas though. Unfortunately I don't think I'll be able to use
the repack locally and then upload strategy for this particular
workflow, but the rsync clone approach might do it.

-Ken

On Sun, Aug 10, 2008 at 4:06 PM, Martin Langhoff
<martin.langhoff@gmail.com> wrote:
quoted text
> On Mon, Aug 11, 2008 at 7:47 AM, Ken Pratt <ken@kenpratt.net> 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@gmail.com
>  martin@laptop.org -- School Server Architect
>  - ask interesting questions
>  - don't get distracted with shiny stuff - working code first
>  - http://wiki.laptop.org/go/User:Martinlanghoff
>



-- 
Ken Pratt
http://kenpratt.net/
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html