Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#71616 - Increase Tier1 requirements and limit to 1 per country (or less).

Attached to Project: Arch Linux
Opened by Niklas Edmundsson (nikke) - Sunday, 25 July 2021, 22:02 GMT
Last edited by Jelle van der Waa (jelly) - Monday, 18 September 2023, 18:01 GMT
Task Type General Gripe
Category Mirrors
Status Closed
Assigned To Anton Hvornum (Torxed)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No



I'm one of the mirror admins for, and recently I revisited to find that not much seems to have changed since we set up our mirror. I don't see our bandwidth of 20 Gbps listed on but perhaps the available bandwidth isn't tracked publicly?

I also looked at sorted by country, and there's a number of countries with a lot of tier1:s. I think this kind of defeats the whole purpose of tier1:s, which is to reduce the load on the master server to provide maximum performance (and minimal mirror distribution delays) to tier1:s, and by that minimize the total time to get all mirrors updated.

I would suggest you to increase/tighten the requirements for new Tier 1 mirrors. In the year of 2021, it would be prudent to require at least 10+ gigabits bandwidth, IPv4+IPv6, http/https/rsync support, and the use of a lastupdate-aware sync script to enable updates more often than hourly (say 4 times per hour). Having Tier 1:s update often kills the argument "I want to update from master because all tier 1:s are behind".

I would also like the requirement that master and tier 1:s have applied TCP tuning to allow for high speed long distance transfers. Due to the bandwidth-delay product, the default Linux 4 MiB TCP buffer size limit really limits transfer speeds between continents and 64 MiB is a more suitable limit for 10 gigabit class hosts. There is a lot of documentation on how to do this on the internet, is one example on how it's done within the Nordic research/HPC community.

Then I would suggest that you start demoting tier1:s in countries with multiple tier1:s that don't make the new requirements (or the old ones, there are currently tier1:s that does not provide rsync or isos). And stick to a limit of one tier1 per country. If tier1:s are good, there shouldn't be a problem for it to handle the tier2:s of that country.

For new Tier 2:s, I would suggest setting a bandwidth requirement of 1 gigabit in countries that already has gigabit-speed mirrors. Users generally aren't helped by more slow mirrors if there already are fast ones.

In general, there should be some wording to discourage servers on home/domestic networks. Even for those with 1 gigabit to the home (like me), the infrastructure of home/domestic internet isn't really built to provide persistent upload performance at that speed, and in the era of work-from-home such servers are likely targets of bandwidth-capping if they interfere with video conferencing and such.

That's it for my general gripe, a very apt description of this I think :-)
This task depends upon

Closed by  Jelle van der Waa (jelly)
Monday, 18 September 2023, 18:01 GMT
Reason for closing:  Moved
Additional comments about closing: rch-mirrors/issues/10
Comment by Jeremy Kescher (kescher) - Tuesday, 02 November 2021, 08:24 GMT
I'll offer my opinions to this gripe (as someone hosting a Tier 2 mirror):

- The number of Tier 1s per country should definitely be limited, however, *not* to a single one per country. But yes, Germany and United States have a lot of mirrors currently (though in the case of the United States, perhaps the difference between US-East and US-West must be noted). A soft upper limit would make sense there, perhaps also the actual physical location within a country can be taken into account there.
- The (advertised) bandwidth offered by a mirror should probably be on the mirror page (perhaps as another table entry).
- Tier 1 requirements: 10 Gbps seems reasonable for new Tier 1s. However, I think even tier 1 mirrors should still be able to decide whether they want to offer http at all. I'm seeing some Tier 1 mirrors that have no rsync support, which doesn't exactly make a lot of sense to me either though. Also, the sync script linked in the Wiki is already lastupdate-aware, so that section should probably be updated.
- Official Tier 2s below 1 Gigabit/s max capacity do not make sense anymore, yes. A lot home users' internet connections can probably saturate a lower bandwidth mirror by now.
Comment by Anton Hvornum (Torxed) - Sunday, 19 February 2023, 16:48 GMT

I'm new to the mirror admin part and just got wind of this ticket.
I've bumped up the bandwidth definition as it was still the 4Gbit from the old days.

I've started a discussion here:
To discussion the rework of Tier 1 requirements and the Tier model as well as it's documentation.

Thank you for the suggestion and initiating a dialogue on the topic.
Comment by Buggy McBugFace (bugbot) - Tuesday, 08 August 2023, 19:11 GMT
This is an automated comment as this bug is open for more then 2 years. Please reply if you still experience this bug otherwise this issue will be closed after 1 month.