Bernd Zeimetz <be...@bzed.de> writes:
> On 08/29/2013 12:13 AM, Ansgar Burchardt wrote:
>> Lucas Nussbaum <lu...@debian.org> writes:
>>> Is there a reason why we couldn't have incoming.d.o apt-able without
>>> lowering the dinstall frequency?
>>
>> That is also possible, however fewer dinstall runs mean less data to
>> push to mirrors and to archive on snapshot.d.o as dists/ would change
>> less often.
>
> How much data are we talking about here? As the built packages need to be
> pushed
> at some point anyway, I guess the only additional data are package
> lists/release
> files and so on?
Right, the packages need to be synced in any case. From a quick look we
have daily changes of:
all year: 2013-01 -- 2013-08: 5852 MB (+- 2808 MB)
post release: 2013-05 -- 2013-08: 7376 MB (+- 2564 MB)
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.
Ansgar
--
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/87mwo154b6....@eisei.43-1.org
