Yaron Scheffer <yschef...@protonmail.com> wrote: > Eric Wong wrote: > > > Yaron: does disabling smart HTTP to rely on only GET transfers > > improve things? Smart HTTP is great for bandwidth reduction but > > uses more CPU/memory on the server side, and perhaps > > recommending clients do that for big repos is a good thing > > anyways for the initial clone. > > > > GIT_SMART_HTTP=0 git clone --mirror ... > > Maybe, but If "git clone" stresses the server to the point of breakage > as you say, something should be done on the server side. I've been > using the kernel.org repo as Konstantin suggested.
Based on Konstantin's message; it didn't seem like the server itself was stressed, just something on Amazon's side. > Perhaps lower the recommended maximum shard size? I didn't hit > this issue with the most recent shard, which is about 50% smaller. That's another option; but migrating/converting existing repos to it would be a flag day and break existing mirrors. ~1G seemed like a reasonable starting point -- unsubscribe: meta+unsubscr...@public-inbox.org archive: https://public-inbox.org/meta/
