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

Re: speeding up git pull from a busy gerrit instance over a slow link?

From
Stefan Beller <sbeller@google.com>
Date
Jun 30, 2017, 22:00 UTC
Message-ID
<CAGZ79kaYYSeyeHpnMuK=+pV+JA-97a=if-AyELvSA4Y5yGhmmg@mail.gmail.com>
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:
Show 23 quoted lines
> 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.)

Previous: Noel Grandin
Message 4 of 4 in “speeding up git pull from a busy gerrit instance over a slow link?”
  1. Noel GrandinJun 30, 2017
  2. Jonathan TanJun 30, 2017
  3. Noel GrandinJul 3, 2017
  4. Stefan BellerJun 30, 2017

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.