Note: Due to technical difficulties, the Archives are currently not up to date.
GMANE provides an alternative service for most mailing lists. c.f. bug 424647
On 06/02/2012 05:32 PM, James Cloos wrote:
> What's up with md5-cache?
>
> Every syn has to pull the entire md5-cache hierarchy over again, as if
> some daemon re-creates every file every day, rather than only re-writing
> those files which need updates and adding/removing those which need that.
We had a bug about that [1] when we first deployed md5-cache, but it's
supposed to have been fixed.
> Even if only the files metatdata changes, that still adds a significant
> cost to an rsync.
>
> It is important that md5-cache files which do not require change be left
> alone.
There's code in portage to avoid redundant cache writes [2]. Eclass
modifications can still trigger lots of cache changes though, especially
eutils.eclass (which most ebuilds inherit).
> Not everyone has gobs of network bandwidth available.
>
> -JimC
[1] https://bugs.gentoo.org/show_bug.cgi?id=410505
[2]
http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=0e120da008c9d0d41c9372c81145c6e153028a6d
--
Thanks,
Zac
|
|
