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, 02:17 UTC
Message-ID
<alpine.LFD.2.00.0911072115270.16711@xanadu.home>
In-Reply-To
<72877ab10911071709s200696d4mf12dc797da20be18@mail.gmail.com>
On Sat, 7 Nov 2009, Tim Webster wrote:
Show 9 quoted lines
> git clone gitosis@gitserver:code.git
> 
> After remote counting objects, remote compressing objects
> transfer begins...
> This compression operation results in excess of swapage on the remote server.
> 
> --------------------
> 
> I need to avoiding the clone compression step for servers with limited memory.

Make sure the remote repository is fully packed. To do so, just go into the remote repository and run 'git gc'.

Nicolas
Previous: Tim WebsterNext: Tim Webster
Message 2 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.