From: Stefan Beller <sbeller@google.com>
To: Noel Grandin <noel@peralex.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: speeding up git pull from a busy gerrit instance over a slow link?
Date: Fri, 30 Jun 2017 15:00:25 -0700 [thread overview]
Message-ID: <CAGZ79kaYYSeyeHpnMuK=+pV+JA-97a=if-AyELvSA4Y5yGhmmg@mail.gmail.com> (raw)
In-Reply-To: <19ee7852-efcc-66d0-24ad-3462a4d5eaf6@peralex.com>
On Fri, Jun 30, 2017 at 5:28 AM, Noel Grandin <noel@peralex.com> wrote:
> Hi
>
> I'm running git version 2.13.1 on Ubuntu 16.04 (x64)
>
> I'm connecting over a very slow (international link) to a very busy gerrit
> server (gerrit.libreoffice.org) using ssh.
> Ping types are on the order of 200ms.
>
> Using GIT_TRACE_PACKET=true, what I am seeing is that the bulk of the time
> is spent retrieving packets having to do with things which I have no
> interest in, i.e. the refs/changes/* stuff (see below).
>
> Is there any way to deliberately exclude these from the pull process?
>
> My git config looks like:
> remote.origin.url=ssh://logerrit/core
> remote.origin.fetch=+refs/heads/*:refs/remotes/origin/*
> branch.master.remote=origin
> branch.master.merge=refs/heads/master
> branch.sdrshapeid.remote=origin
> branch.sdrshapeid.merge=refs/heads/master
>
> Thanks, Noel Grandin
From here I figured, you're talking about gerrit.libreoffice.org/core
My initial clone is taking rather long, it was stuck in the
"Counting objects" phase for quite some time. Maybe ask the
Gerrit administrator if they have pack.useBitmaps enabled?
(This is a tangent, and most likely related to the initial clone only,
you are asking for everyday fetches.)
prev parent reply other threads:[~2017-06-30 22:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-30 12:28 speeding up git pull from a busy gerrit instance over a slow link? Noel Grandin
2017-06-30 21:59 ` Jonathan Tan
2017-07-03 7:01 ` Noel Grandin
2017-06-30 22:00 ` Stefan Beller [this message]
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='CAGZ79kaYYSeyeHpnMuK=+pV+JA-97a=if-AyELvSA4Y5yGhmmg@mail.gmail.com' \
--to=sbeller@google.com \
--cc=git@vger.kernel.org \
--cc=noel@peralex.com \
/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).