all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Random idea about speeding up guix pull
Date: Tue, 05 Sep 2017 16:33:53 +0200	[thread overview]
Message-ID: <87d175qkoe.fsf@gnu.org> (raw)
In-Reply-To: <216b2dc5-efa3-d052-9f68-7d1792cc98ec@crazy-compilers.com> (Hartmut Goebel's message of "Tue, 5 Sep 2017 14:23:15 +0200")

Hartmut Goebel <h.goebel@crazy-compilers.com> skribis:

> Am 04.09.2017 um 23:56 schrieb Ludovic Courtès:
>> What it does do is maintain a cached checkout in ~/.cache/guix/pull,
>> which makes subsequent pulls much faster.
>
> Summary ( TL;DR):
>
>   * "guix pull" should use "git fetch master"
>   * "guix download" we can keep the current behaviour
>
> I did a series of tests
>
>   * - "fetch" without any argument will fetch *all* data from *all*
>     branches.
>   * - "fetch master" only fetches data living on "master", other
>     branches are ignored
>
> I compared the data fetched for a repo with status of 6bd1c41e8
> (yesterday 05:29):
>
>   * - "fetch" fetches 1000K
>   * - "fetch master" fetches 755K
>   * - "fetch --depth=1 master" fetches 588K (but see below)

Thanks for the detailed analysis!

The problem is that libgit2 doesn’t support shallow clones, and it’s
unclear whether it will support it in the future:

  https://github.com/libgit2/libgit2/issues/3058

:-/

Ludo’.

  reply	other threads:[~2017-09-05 14:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-03 14:27 Random idea about speeding up guix pull Hartmut Goebel
2017-09-03 14:38 ` ng0
2017-09-04 15:01 ` Ludovic Courtès
2017-09-04 15:39   ` Hartmut Goebel
2017-09-04 21:56     ` Ludovic Courtès
2017-09-05 12:23       ` Hartmut Goebel
2017-09-05 14:33         ` Ludovic Courtès [this message]
2017-09-05 14:51           ` Hartmut Goebel
2017-09-07  8:28             ` Ludovic Courtès

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=87d175qkoe.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=h.goebel@crazy-compilers.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. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.