From: Brian Harring <ferringb@gmail.com>
To: robbat2@gentoo.org
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: metadata/md5-cache
Date: Mon, 4 Jun 2012 16:56:43 -0700 [thread overview]
Message-ID: <20120604235643.GD3692@localhost> (raw)
In-Reply-To: <robbat2-20120603T085959-907082290Z@orbis-terrarum.net>
On Sun, Jun 03, 2012 at 09:25:43AM +0000, Robin H. Johnson wrote:
> On Sun, Jun 03, 2012 at 08:31:43AM +0000, Duncan wrote:
> > Micha?? G??rny posted on Sun, 03 Jun 2012 09:22:04 +0200 as excerpted:
> >
> > >> Even if only the files metatdata changes, that still adds a significant
> > >> cost to an rsync.
> > > I wonder when it will come to the point where git will be more efficient
> > > than rsync. Or maybe it would be already?
> > Handwavey guess, but I've figured git to be more efficient client-side
> > for some time. Server-side I don't know about, but I've presumed that's
> > the reason the switch-to-git plans haven't included switching the default
> > for user-syncs to git. I expect user/client side, git would be more
> > efficient already, but as I said, that's handwavey guesses.
> No, the switch to git will NOT help users, it isn't more efficient.
>
> They will still be best served by rsync, for a couple of reasons:
> 1. metadata cache is NOT available in Git.
Sidenote, and this is mildly insane, I'd thought about submodules for
this; basically every rsync window, we dump the metadata into vcs,
which devs can pull down and make use of.
I've also not experimented w/ this workflow, so it could be batshit
insane. Anyone game to experiment?
~harring
prev parent reply other threads:[~2012-06-04 23:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-03 0:32 [gentoo-dev] metadata/md5-cache James Cloos
2012-06-03 0:54 ` Zac Medico
2012-06-03 3:52 ` James Cloos
2012-06-03 6:41 ` Zac Medico
2012-06-03 7:22 ` Michał Górny
2012-06-03 8:31 ` [gentoo-dev] metadata/md5-cache Duncan
2012-06-03 9:25 ` Robin H. Johnson
2012-06-03 9:34 ` Michał Górny
2012-06-03 9:48 ` Robin H. Johnson
2012-06-04 7:27 ` Michał Górny
2012-06-04 13:15 ` Brian Harring
2012-06-04 23:56 ` Brian Harring [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=20120604235643.GD3692@localhost \
--to=ferringb@gmail.com \
--cc=gentoo-dev@lists.gentoo.org \
--cc=robbat2@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