From ArchWiki
Revision as of 19:03, 20 June 2019 by OakeyN (talk | contribs) (pls add syncrepo)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
  • someone could please add description about the storage requirement of a archlinux mirror? --Rae 10:46, 28 June 2010 (EDT)
  • added --Romashka
  • i believe we should have an reference script here (maybe the links?) Pierre has some scripts but there's no explanation about them. -- tunix
  • Storage size for the repos is out of date. as of NOV 20, 2011: community->31G, core->460M, extra->11G, multilib->229M. others may need updating too.-- surlyjake
  • How much traffic should one expect from syncing alone? ernetas
  • The storage size is really out of date, as of 22.04.2014: iso->5G, pool/packages->11G, pool/community->26G, altogether around 42G. Goll
  • As for the traffic information, I can give an example from a Tier 2 mirror as of 22.04.2014, monthly outgoing traffic is around 200 GB, weekly unique IP's around 10.000. Goll
  • Typo in the Tier 2 requirements section: "If you ever whish to send downtime notifications" <-- should be wish -- sudokode 2016/05/08 13:10 UTC
  • The size information is out-of-date again. I synced off a Tier 1 today and received a pool of 48G (instead of 41G noted in the article). -- Majewsky (talk) 22:13, 19 October 2016 (UTC)
    • Updated, thanks --Bluewind (talk) 14:30, 25 October 2016 (UTC)
  • Would you like linking syncrepoAUR in "You can use rsync directly or this script as a starting point."

Outdated bandwidth limit note

"You can use rsync directly or this script as a starting point. Please note that the script tries to minimize load and bandwidth used (about 5MiB as of 2014-01-21) in case there are no changes. Feel free to remove this check if you don't sync very often or your upstream mirror does not provide the lastupdate file."

The bolded part is outdated, the script now has bandwidth limit set to 0 (no bandwidth limit) by default.

--VictorBjelkholm (talk) 11:44, 1 March 2018 (UTC)

This is actually not what the text tried to tell you. What the script prevents is rsync from running unnecessarily because each time rsync is run, it has to check for all files if there are differences in size, modification time, ... . This metadata is quite large and if you run rsync very often, like e.g. every minute, it adds up to some hundred gigabytes of unnecessary traffic per month. I've changed the text so it's hopefully a bit clearer now. Bluewind (talk) 12:03, 1 March 2018 (UTC)
Thanks, makes sense and reading the script again, I can see that happening. Thanks a lot for the quick clarification. VictorBjelkholm (talk) 12:04, 1 March 2018 (UTC)