From: Joshua Jensen <jjensen@workspacewhiz.com>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: git-upload-pack bandwidth cap over SSH?
Date: Fri, 24 Sep 2010 13:30:30 -0600 [thread overview]
Message-ID: <4C9CFC56.3030501@workspacewhiz.com> (raw)
In-Reply-To: <4C9CB9E9.8010901@workspacewhiz.com>
----- Original Message -----
From: Joshua Jensen
Date: 9/24/2010 8:47 AM
> Our Git repository central server is running on some kind of
> enterprise VM software. I can push repository changes through the
> Gitolite-monitored SSH tunnel at 10+ megabytes per second.
>
> A 'git pull' operation (even a fresh clone of the packed repository)
> always caps at 1.55 MiB/s, according to the "Receiving objects" line
> in the status text.
>
> Thinking it might be a hardware issue (half duplex?), I installed
> VirtualBox on my Windows 7 64-bit machine and then made an Ubuntu
> Gitolite install. Running on my local hardware, the push is roughly
> 12 megabytes per second. The 'git pull' downstream again caps at 1.55
> MiB/s.
>
> Are there any configuration settings within Git that may limit the
> git-upload-pack operation's speed?
>
> I realize this could be a MinGW issue via the msysGit client.
>
> Update: I just copied a large file via 'scp', and the downstream still
> capped at 1.55-ish megabytes per second. So it isn't Git.
Replying to my own message... I take that back. I'm not sure what I was
seeing, but I can consistently run scp and copy files at 6+ megabytes
per second.
With that in mind, I'm back to looking at Git's pull performance over
SSH. It never exceeds 1.55 MiB/s.
Josh
next prev parent reply other threads:[~2010-09-24 19:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-24 14:47 git-upload-pack bandwidth cap over SSH? Joshua Jensen
2010-09-24 16:16 ` Matthieu Moy
2010-09-24 19:13 ` Tay Ray Chuan
2010-09-24 19:30 ` Joshua Jensen [this message]
2010-09-24 19:42 ` Joshua Jensen
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=4C9CFC56.3030501@workspacewhiz.com \
--to=jjensen@workspacewhiz.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;
as well as URLs for NNTP newsgroup(s).