Ansgar Burchardt wrote:
> In comparison the changing part of unstable:
>
> $ du -shc dists/unstable/*/{binary-*,source,Contents*.gz} | tail -1
> 665M total
>
> So having two dinstall runs per day compared to four would reduce the
> amount of changes by roughly 1.3 GB per day. Mirrors also profit from
> rsyncable gzip files, but snapshot.d.o does not.
>
> I'm not sure how much dists/ changes in total: I think unstable changes
> between every run, but testing changes at most twice a day. And then
> there are smaller suites (experimental, proposed-updates, ...). My guess
> is that it's about
>
> 4* 665 MB (unstable)
> 1-2* 563 MB (testing)
> 1-2* 70 MB (experimental)
>
> So maybe 3293-3926 MB per day, i.e. about half of the actual package
> changes.
Could dinstall frequency vary by architecture? Most of the benefit in
frequent dinstall runs comes from AMD64, but most of the cost comes from
unimportant architectures. So if there are resource limits, it'd make
sense to concentrate the resources on the architectures that matter.
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/1377786085.12282.8.camel@glyph.nonexistent.invalid
