git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: performance issue: git clone compression

From
Nicolas Pitre <nico@fluxnic.net>
Date
Nov 8, 2009, 03:04 UTC
Message-ID
<alpine.LFD.2.00.0911072155180.16711@xanadu.home>
In-Reply-To
<72877ab10911071845q1c60e2b0kfe6f0509b5728912@mail.gmail.com>
On Sat, 7 Nov 2009, Tim Webster wrote:
> On servers with limit memory it is not piratical to run git gc.
> I can run git gc on a bare mirror and rsync back to the server.

That is fine. As long as you end up with a single pack, then a clone would basically be a sinple file transfer.

Also you might want to investigate the following config variable for a low-memory server:

	core.packedGitWindowSize
	core.packedGitLimit
	pack.windowMemory
	pack.deltaCacheSize
	pack.deltaCacheLimit
Nicolas
Previous: Tim Webster
Message 4 of 4 in “performance issue: git clone compression”
  1. Tim WebsterNov 8, 2009
  2. Nicolas PitreNov 8, 2009
  3. Tim WebsterNov 8, 2009
  4. Nicolas PitreNov 8, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.