Description of problem: The mirror api currently returns south american mirrors for south american countries. The problem is, that there isn't ISP interconnection between south american countries, so all connections have to go through the US, making the downloads slower. I'm completely sure of this with Colombia, please see this: This first test is to my current mirror on Brazil: http://www.speedtest.net/result/1689380404.png Ping: 211ms Download speed: 3.23Mb/s Upload speed: 1.02Mb/s This one is with a Server on US, Florida: http://www.speedtest.net/result/1689383587.png Ping: 84ms Download speed: 4.34Mb/s Upload speed: 1.07Mb/s As you can see, US server are much faster for Colombia than any south american server. And I'm pretty sure this is the same case for other countries too. Here's a tracepath for the mirror in Brazil and one on the US: [mageia@dci-laptop ~]#tracepath mageia.c3sl.ufpr.br 1: dci-laptop.local 0.167ms pmtu 1500 1: 192.168.1.1 2.489ms 1: 192.168.1.1 1.394ms 2: Dynamic-IP-186821441.cable.net.co 22.459ms 3: 172.31.252.218 12.475ms 4: Static-IP-1901577149.cable.net.co 19.972ms 5: 10.14.14.74 75.081ms asymm 9 6: 64.86.28.41 80.586ms asymm 7 7: 216.6.48.6 72.911ms asymm 9 8: te1-1.miami14.mia.seabone.net 94.378ms asymm 7 9: fiu.miami14.mia.seabone.net 78.967ms asymm 11 10: ae4-540-r0-sp.bkb.rnp.br 183.890ms asymm 11 11: xe-2-1-1-3000-r0-pr.bkb.rnp.br 191.368ms asymm 12 12: as10881.pr.ptt.br 194.640ms asymm 13 13: c3sl-ge-1-5-r2.pop-pr.rnp.br 192.768ms asymm 14 14: sagres.c3sl.ufpr.br 194.544ms reached Resume: pmtu 1500 hops 14 back 50 As you can see on hop #8, for going to Brazil, the connection reached Miami and then jumped to brazil (through a really loooooong connection). As a difference, see how's with a US server: [root@dci-laptop ~]# tracepath mirrors.kernel.org 1: dci-laptop.local 0.095ms pmtu 1500 1: 192.168.1.1 2.795ms 1: 192.168.1.1 8.007ms 2: Dynamic-IP-186821441.cable.net.co 19.685ms 3: 172.31.252.218 11.916ms 4: 190.85.254.25 11.592ms 5: 10.14.14.74 83.221ms asymm 9 6: 64.86.28.41 70.885ms asymm 7 7: if-5-1343.tcore2.DT8-Dallas.as6453.net 129.371ms asymm 12 8: if-2-2.tcore1.DT8-Dallas.as6453.net 142.018ms asymm 11 9: 64.86.78.5 140.796ms 10: int-0-2-202.r1.ord1.isc.org 145.432ms 11: int-0-0-1-8.r1.pao1.isc.org 171.126ms asymm 10 12: mirrors2.kernel.org 169.823ms reached Resume: pmtu 1500 hops 12 back 54 It has a shorter route and smaller response times. Also as currently there's only one server in Brazil, when it fails all south american users are screwed (like right now that core/release for that mirror is returning 404 for hdlists). So what I'm asking if at least Colombia can be mapped to US servers, preferably on the East coast.
Can someone take a look at this please ? having to download packages from the brazil mirror at not more than 60 - 70k with a 4Mbps bandwidth is ridiculous. I know I can manually change the mirror but that's not the point.
iirc the mirrorlist does'nt use the localization.
IIRC, it has a mapping somewhere, before the Brazil mirror, we were being assingned a mirror in Guatemala (which also was closer to south america) every time too. Every time I remove & re-add the mirrors using urpmi.addmedia --distrib --mirrorlist I will get that Brazil mirror. I have checked this with at least two more machines in the same city with the same result. But with another one on the US, a US server is selected.
I think the heuristics here are in the client software, not on the server (which only provides the full mirrors list at this time).
CC: (none) => rdalverny
CC: (none) => filip.komarDepends on: (none) => 17400
Can you please retest as the selection code is changed?
(In reply to Filip Komar from comment #5) > Can you please retest as the selection code is changed? For the DL web page not the mirror API itself.
(In reply to Filip Komar from comment #5) > Can you please retest as the selection code is changed?