public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Zac Medico <zmedico@gentoo.org>
To: Alec Warner <antarus@gentoo.org>,
	gentoo-project <gentoo-project@lists.gentoo.org>,
	Zac Medico <zmedico@gentoo.org>
Subject: Re: [gentoo-project] RFC: Dropping rsync as a tree distribution method
Date: Sat, 15 Dec 2018 23:42:01 -0800	[thread overview]
Message-ID: <9967b600-0048-0597-9b8b-6076e163179b@gentoo.org> (raw)
In-Reply-To: <CAAr7Pr_XvmEPTi11He3b+5dFN5=aFVwFZVBLt6zeBUTtZoYsYg@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2653 bytes --]

On 12/15/18 9:17 PM, Alec Warner wrote:
> 
> 
> On Sun, Dec 16, 2018 at 12:13 AM Georgy Yakovlev <gyakovlev@gentoo.org
> <mailto:gyakovlev@gentoo.org>> wrote:
> 
>     On Saturday, December 15, 2018 8:40:38 PM PST Matt Turner wrote:
>     > On Sat, Dec 15, 2018 at 11:16 PM Alec Warner <antarus@gentoo.org
>     <mailto:antarus@gentoo.org>> wrote:
>     > > - Disk usage for git vs rsync
>     >
>     > This is why I have not switched. With git you pull down increasing
>     > amounts of history, whereas with rsync the data fits easily in a <1GB
>     > partition.
> 
>     Recent portage can use sync-depth = 1
>     repo dir no longer grows as it used to and it's works fine unlike
>     initial
>     implementation that was giving trouble
> 
>     https://bugs.gentoo.org/552814
> 
>     du -hs /var/db/repos/gentoo
>     350M    /var/db/repos/gentoo
> 
>     example /etc/portage/repos.conf/gentoo.conf :
>     [DEFAULT]
>     main-repo = gentoo
> 
>     [gentoo]
>     auto-sync = yes
>     location = /var/db/repos/gentoo
>     sync-type = git
>     sync-uri = https://github.com/gentoo-mirror/gentoo.git
>     sync-depth = 1
>     sync-git-clone-extra-opts = -b master
>     sync-git-verify-commit-signature = true
> 
> 
>     sync is almost instantaneous compared to rsync, but some folks not
>     going to
>     like github as a mirror in this case.
> 
> 
> I don't plan on using github for the mirror, so I'm not overly worried
> about that portion.
> 
> +Zac Medico <mailto:zmedico@gentoo.org> 
> 
> My recollection was that git doesn't ship with ebuild metadata by
> default, so even if we make the first sync fast (by using depth=1 in the
> clone) do we have a good story for ebuild metadata? Is portage just
> faster than in the past for ebuilds with missing metadata? Does emerge
> --sync handle metadata regen for syncs with git origins?
> 
> -A

The metadata has to be included in the git repostory, and we've
currently got "master" and "stable" branches which include everything
that the rsync tree has:

https://gitweb.gentoo.org/repo/sync/gentoo.git/log/?h=master
https://gitweb.gentoo.org/repo/sync/gentoo.git/log/?h=stable

Both branches are also mirrored on github:

https://github.com/gentoo-mirror/gentoo/commits/master
https://github.com/gentoo-mirror/gentoo/commits/stable

It would be interesting to see some garbage collection stats for
sync-deph = 1, people using it should post the output of this command:

git count-objects -v

>  
> 
> 
> 
>     -- 
>     Georgy Yakovlev
>     Gentoo Linux Developer
> 


-- 
Thanks,
Zac


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 981 bytes --]

  parent reply	other threads:[~2018-12-16  7:42 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-16  4:15 [gentoo-project] RFC: Dropping rsync as a tree distribution method Alec Warner
2018-12-16  4:40 ` Matt Turner
2018-12-16  5:13   ` Georgy Yakovlev
2018-12-16  5:17     ` Alec Warner
2018-12-16  6:50       ` Raymond Jennings
2018-12-16  6:52         ` Raymond Jennings
2018-12-16  7:38       ` Zac Medico
2018-12-16  7:42       ` Zac Medico [this message]
2018-12-18 17:28         ` Andrew Savchenko
2018-12-16  6:55     ` Raymond Jennings
2018-12-16 10:22     ` Toralf Förster
2018-12-17 17:26     ` Matt Turner
2018-12-17 17:43       ` Raymond Jennings
2018-12-18  3:57         ` Georgy Yakovlev
2018-12-18  4:02           ` Raymond Jennings
2018-12-18  8:06           ` Robin H. Johnson
2018-12-20  1:18           ` Kent Fredric
2018-12-16 11:34 ` Rich Freeman
2018-12-16 21:10   ` Matthew Thode
2018-12-20  1:26   ` Kent Fredric
2018-12-16 17:15 ` Toralf Förster
2018-12-16 17:38   ` M. J. Everitt
2018-12-16 18:05     ` M. J. Everitt
2018-12-16 18:36       ` Rich Freeman
2018-12-16 18:41         ` M. J. Everitt
2018-12-18  9:55 ` Andrew Savchenko
2018-12-18 11:36   ` Raymond Jennings
2018-12-18 17:14     ` Andrew Savchenko
2018-12-18 18:00       ` Alec Warner
2018-12-18 22:13         ` M. J. Everitt
2018-12-18 11:55   ` Michał Górny
2018-12-20  1:43   ` Kent Fredric
2018-12-20  2:33     ` Rich Freeman
2018-12-20 16:21       ` Kent Fredric
2018-12-18 18:14 ` Brian Evans
2018-12-18 18:37   ` Alec Warner
2018-12-18 18:38     ` Raymond Jennings
2018-12-18 20:29       ` Alec Warner
2018-12-18 18:42   ` Rich Freeman
2018-12-19 23:46   ` Robin H. Johnson

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=9967b600-0048-0597-9b8b-6076e163179b@gentoo.org \
    --to=zmedico@gentoo.org \
    --cc=antarus@gentoo.org \
    --cc=gentoo-project@lists.gentoo.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