On 01/30/17 at 08:39pm, Florian Pritz via arch-dev-public wrote: > Hi, > > I've just received a report from a mirror admin about some very heavy > traffic. After some investigation it appears that the traffic towards > his mirror started to rise around the beginning of the new year when we > disabled the mirror checker on gerolde. Since we now only have a mirror > checker running in Germany and his server is actually in the same data > centre as ours, the mirror checks completed very quickly.
I can't think of an elegant solution for this issue. > I'm thinking about removing the mirror score from archweb's output and > more importantly, not sorting mirrors based on this score but rather > randomizing the list returned in [2]. It could still take the score into > account by limiting the returned set to mirror that are not totally out > of date, but I'd remove the sorting. The score doesn't really have a lot > a meaning anyways since it's just from our point of view. > > Does anyone have hard feeling about this? If not I'll prepare a patch in > the next few days. Idea sounds good to me, don't forget that you can also 'generate a mirrorlist' here, so you might want to remove the 'use mirror status' option there too. (or was that not part of the plan?) [1] [1] https://www.archlinux.org/mirrorlist/ -- Jelle van der Waa
signature.asc
Description: PGP signature
