From: Matthew Thode <prometheanfire@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] RFC: Dropping rsync as a tree distribution method
Date: Sun, 16 Dec 2018 15:10:07 -0600 [thread overview]
Message-ID: <20181216211007.3if7u53d5tpcetap@gentoo.org> (raw)
In-Reply-To: <CAGfcS_=n_JBEx5vubFVEXH6ZUrKgMN3f=HHjtfW1eGOe=W0BBw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1956 bytes --]
On 18-12-16 06:34:07, Rich Freeman wrote:
> On Sat, Dec 15, 2018 at 11:15 PM Alec Warner <antarus@gentoo.org> wrote:
> >
> > [1] Rich talked about some downsides earlier at https://lwn.net/Articles/759539/; but while these are challenges (some fixable) they are not necessarily blockers.
>
> The thread has already touched on a few of those comments. Despite
> only six months elapsing since I wrote that email, #1 no longer
> applies, and it sounds like #4 may not be as much of a concern. As
> you've already stated #3 can be easily addressed - setting up a git
> mirror is very easy.
>
> I think #2 is more of a fundamental design difference that probably
> will never go away. If your tree is a year old then git WILL take
> longer and transfer more data than rsync. My guess is that it will
> also cost more IO server-side than rsync, but it probably will be
> cheaper in CPU. However, I bet that 95% of our users sync weekly or
> daily and in that use case it is going to go a lot faster, and
> probably be less mirror load as well, and it will be a TON less IO
> load on the client side. I'm not sure how much IO cost there is to
> git garbage collection - that might offset this in the common shallow
> clone scenario.
>
> I'd suggest that those with concerns give it a shot using Zac's
> suggested settings and see how it goes. Really all you have to do is
> delete your local repo and adjust your sync settings and resync. I
> think the local disk use is going to be the biggest source of user
> objection and I'm interested in what people observe here.
>
I wonder if we can add a little logic to help at least a little bit on
the yearly syncers. If over a 6 months, remove old git sync'd dir and
replance with new shallow clone? Not perfect, but workable maybe.
Do we need to tell users to set up a git gc cron job or does portage
handle that for us now?
--
Matthew Thode (prometheanfire)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-12-16 21:10 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
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 [this message]
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=20181216211007.3if7u53d5tpcetap@gentoo.org \
--to=prometheanfire@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