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

performance issue: git clone compression

From
TWTim Webster <tdwebste@gmail.com>
Date
Nov 8, 2009, 01:09 UTC
Message-ID
<72877ab10911071709s200696d4mf12dc797da20be18@mail.gmail.com>
In-Reply-To
<72877ab10911071657p568b3b98v6fd90e84e098c107@mail.gmail.com>
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. I am doing the following to avoid this object compression. Is there a better way? -------------------

scp -r gitserver:/srv/gitosis/repositories/code.git  . git clone /tmp/junk/code.git --no-hardlinks code # IS there a better way of converting the bare git repository to working git repository?

edit .git/config url = gitosis@gitserver:code.git

Next: Nicolas Pitre
Message 1 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.