Hi Slavek,

Thank you for the comprehensive response.  A few points come to mind.


(1) TDE mirrors are not synced "daily".

    Due to master server bandwidth limitations, primary sync runs can
    take anywhere from a minute to a week.

    The primary mirror normally syncs from Tim's master server
    continuously subject to a bandwidth limit selected by Tim and
    with a short delay between the completion of one sync run
    and the start of the next.  During major release rollouts
    syncing is changed e.g. by reducing delay between sync runs
    and by deferring dbg/debuginfo/dev/devel/tar/src files when more
    urgent files need to be mirrored.

    Secondary mirrors sync from the primary on their own schedules.
    Currently some secondaries sync three times per day and some four.


On Sat July 21 2018 10:20:33 Sl�vek Banko wrote:
> On Sunday 24 of June 2018 20:59:46 Mike Bird wrote:
> > (6) To avoid overloading build farm bandwidth, it is best not to
> > announce releases until they are fully mirrored.  If users start
> > pulling unmirrored files they are served from the build farm,
> > overloading its bandwidth and slowing mirroring, so things get very
> > slow for everyone.
>
> This is no longer necessary. As I mentioned above, the redirector has a
> cache that is filled with new packages before the official release.
> Therefore, at the time of release, if packages are not yet available on
> official mirrors, they may be served directly from this cache. This makes
> the packages available to users quickly and without overloading the line
> to the primary server.

(2) This seems counter-productive.  The reason for implementing a
    distinct primary mirror was so that each file would only be
    transferred once from Tim's master server due to bandwidth
    limitations.


> Already R14.0.4 has successfully used this cache at the time of release.

(3) There were severe slowdowns for several days during R14.0.4 rollout
    which appeared to be due to master server bandwidth limitations.


--Mike