| 1 |
On 06/02/2012 05:32 PM, James Cloos wrote: |
| 2 |
> What's up with md5-cache? |
| 3 |
> |
| 4 |
> Every syn has to pull the entire md5-cache hierarchy over again, as if |
| 5 |
> some daemon re-creates every file every day, rather than only re-writing |
| 6 |
> those files which need updates and adding/removing those which need that. |
| 7 |
|
| 8 |
We had a bug about that [1] when we first deployed md5-cache, but it's |
| 9 |
supposed to have been fixed. |
| 10 |
|
| 11 |
> Even if only the files metatdata changes, that still adds a significant |
| 12 |
> cost to an rsync. |
| 13 |
> |
| 14 |
> It is important that md5-cache files which do not require change be left |
| 15 |
> alone. |
| 16 |
|
| 17 |
There's code in portage to avoid redundant cache writes [2]. Eclass |
| 18 |
modifications can still trigger lots of cache changes though, especially |
| 19 |
eutils.eclass (which most ebuilds inherit). |
| 20 |
|
| 21 |
> Not everyone has gobs of network bandwidth available. |
| 22 |
> |
| 23 |
> -JimC |
| 24 |
|
| 25 |
[1] https://bugs.gentoo.org/show_bug.cgi?id=410505 |
| 26 |
[2] |
| 27 |
http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=0e120da008c9d0d41c9372c81145c6e153028a6d |
| 28 |
-- |
| 29 |
Thanks, |
| 30 |
Zac |
Archives