this post was submitted on 19 Jun 2023
9 points (100.0% liked)

Arch Linux

8557 readers
1 users here now

The beloved lightweight distro

founded 5 years ago
MODERATORS
 

I used to pick out mirrors manually and had servers very close to me, but I recently started using reflector to automate the process, but the mirrors it chooses is absolute dogshit and gives me really slow speeds.

What am I doing wrong?

top 9 comments
sorted by: hot top controversial new old
[–] theophrastus@vlemmy.net 4 points 2 years ago (1 children)

Could you include what you're currently using for the various reflector command-line switches? (e.g. --age --protocol --sort ...)

[–] radicalpikachu@vlemmy.net 1 points 2 years ago (3 children)

Here's whats in /etc/xdg/reflector/reflector.conf


# Reflector configuration file for the systemd service.
#
# Empty lines and lines beginning with "#" are ignored.  All other lines should
# contain valid reflector command-line arguments. The lines are parsed with
# Python's shlex modules so standard shell syntax should work. All arguments are
# collected into a single argument list.
#
# See "reflector --help" for details.

# Recommended Options

# Set the output path where the mirrorlist will be saved (--save).
--save /etc/pacman.d/mirrorlist

# Select the transfer protocol (--protocol).
--protocol https

# Select the country (--country).
# Consult the list of available countries with "reflector --list-countries" and
# select the countries nearest to you or the ones that you trust. For example:
--country Bangladesh,India

# Use only the  most recently synchronized mirrors (--latest).
--latest 5

# Sort the mirrors by synchronization time (--sort).
--sort age
[–] theophrastus@vlemmy.net 1 points 2 years ago (1 children)

i believe that is what will be used by reflector if it is enabled/started as a systemd service. but, i think, that'll not be used if you're just calling it on the command-line. in that latter case, i think you must supply (those) command-line switches on ...the command-line. (maybe)

[–] radicalpikachu@vlemmy.net 0 points 2 years ago (1 children)

The systemd service is enabled, and when I did actually apply all these in the command line manually too before enabling the service.

[–] theophrastus@vlemmy.net 1 points 2 years ago

ah. now armed with that extra information, i can only profess cluelessness. perhaps a "--verbose" option, well watched, would reveal something (maybe) good luck!

[–] 4ffy@lemmy.ml 1 points 2 years ago* (last edited 2 years ago)

In my reflector.conf, I have --score 5 instead of --latest 5. I don't know how much this actually improves anything, but surely selecting by score is better than just using the most recently updated mirrors.

[–] festus@lemmy.ca 1 points 2 years ago* (last edited 2 years ago)

Been a while since I mucked with reflector, but you don't seem to be prioritizing faster mirrors whatsoever. Try --sort rate instead. If that's not fast enough I'd also increase your --latest up to maybe 15 so that you have higher odds of a fast mirror being in the group of just-updated mirrors.

[–] memchr@lemmy.world 2 points 2 years ago

A bit off topic:

Normally the mirrors behind the CDN would have decent speeds everywhere, e.g.

  • mirror.osbeck.com
  • arch.hu.fo
  • mirror.sunred.org

These are the top tree mirrors currently on the mirror status and they are all behind cloudflare.

[–] Supermariofan67@lemmy.fmhy.ml 1 points 2 years ago

Reflector is broken now because it's hardcoded to test the community.db file, but that file is now just an empy stub as that repo was merged into extra. Reflector is just a python script so you could edit it to replace mention of community.db with extra.db until the devs fix it.