From: Tim Webster <tdwebste@gmail.com>
To: git@vger.kernel.org
Subject: performance issue: git clone compression
Date: Sat, 7 Nov 2009 17:09:59 -0800 [thread overview]
Message-ID: <72877ab10911071709s200696d4mf12dc797da20be18@mail.gmail.com> (raw)
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 parent reply other threads:[~2009-11-08 1:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <72877ab10911071657p568b3b98v6fd90e84e098c107@mail.gmail.com>
2009-11-08 1:09 ` Tim Webster [this message]
2009-11-08 2:17 ` performance issue: git clone compression Nicolas Pitre
2009-11-08 2:45 ` Tim Webster
2009-11-08 3:04 ` Nicolas Pitre
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=72877ab10911071709s200696d4mf12dc797da20be18@mail.gmail.com \
--to=tdwebste@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox