At this point I’m not sure what to do? The download speeds for my Tumbleweed Zypper Dup is so incredibly slow. Sometimes it takes like 10 to 20 seconds to download a 15MB file. I live on the east coast of the USA. Supposedly download.opensuse.org should be directing me to mirrorcache-us.opensuse.org for the fastest mirror because of geoip.
However, I just checked mirrorcache-us.opensuse.org and it’s currently down. Upon checking online history and on reddit, the USA apparently has its mirrorcache frequently down and at times for days.
Should I just be putting a mirror manually myself or should I switch to cdn.opensuse.org(not sure if that will make a difference). There has to be a reason why it’s pulling from mirrors that are further away. I’m not sure if there is a lack of mirrors here in the USA or if they are out of date. It would be silly if my zypper is pulling from europe or even further.
Have you looked at general network performance with your connection? I’d be inclined to try tracing the route and look at latencies there to see if there might be any potential issues exposed that way.
I’ll give that a shot and see if it helps. I live here in Florida and it seems the download speeds are abysmal at times even for tiny files that are MB in size. There are times the download rates are close to dial-up days. I suspect it has something to do with with the mirrors and which one its pulling from. Mind you I’m not expecting blazing speeds or anything, but at times it just seems so incredibly slow.
Is there any options I should be looking in the Zypper configs?
cdn.o.o is super fast now. Try it!
Previously for me anyway it would pull only the metadata from it and the package binaries themselves were downloaded from locally redirected mirrors, now it pulls the binaries from the CDN itself and is fast
You could try using ‘techpreview.ZYPP_MEDIANETWORK=1’ as well - it’s a preview feature that changes the HTTP backend and is an async downloader. If the problem is network-related, it may not help, but if there’s something else go on, it might.
Changing it to cdn.opensuse.org did increase the speed by around 40% or so. It’s not a huge significant leap ahead in speed but definitely much better then what I was getting on download.opensuse.org. The only thing I can think of is that the nearby mirrors are actually further then I expected.
mirrorcache-us.opensuse.org is working today but it was down quite a bit last 2 days. I don’t know if cdn.opensuse.org points to it or uses their own system to evaulate nearest mirrors.
cdn uses a different infrastructure than mirrorcache, as I understand it. download.opensuse.org uses mirrorcache (again, as I understand it).
I would definitely be inclined to see if other downloads are similarly slowed. If your ISP (or an upstream provider) is throttling speeds or is oversaturated, there’s nothing the openSUSE infrastructure could do that would improve the speeds.
ISPs typically oversubscribe their bandwidth, so if more people are using bandwidth across a particular hop between you and the servers, that’s going to impact your performance (along with everyone else’s). That’s why I’d look at things like latency with traceroute. Downloading directly from other sites can be useful, but only if those downloads follow a similar route - if the bottleneck is somewhere between you and the mirror you’re hitting, and you download from somewhere that doesn’t hit that bottleneck, you will get different results.
Sometimes, a traceroute will not show where the problem is. I just ran a traceroute to cdn.o.o. The traceroute shows addresses for the first 11 hops, all of which are on my home ISP. Hops 12 through 30 all display three asterisks.
A separate traceroute to mirrorcache-us.o.o completes, all hops except the last four are also on my home ISP. It routed to Utah, which is probably slc-mirror.
Like the OP, I’m also on the east coast of the U.S.
I too am in FL, and use TW, Slowroll and Leap on multiple multiboot PCs. IMO, poor throughput is related to the fact that not all North American repos are full service, meaning some only provide Leap, while others omit “repositories”, or selected other repo directories. I have multiple repo files for each repo, but only one per repo whose filename ends in .repo, thus never are any duplicates found by zypper or yast. It’s a simple matter of a file copy in /etc/zypp/repos.d/ with one or two letters removed to switch any particular repo definition to some other mirror. My initial experiences with mirrorcache.o.o were terrible, so I haven’t tried it since its inception. Some other than download.o.o. and cdn.o.o here include: Georgia Tech, Leaseweb US, Leaseweb Miami, Leaseweb Dallas, Leaseweb WDC, gwdg.de, kernel.org & provo. Normally I use d.o.o, finding it to be on average best compromise. Leaseweb Miami is normally fast, but it isn’t complete, apparently like all Leasewebs, so good mainly for Leap.
