FS#36484 - Pacman's low speed download

Attached to Project: Pacman
Opened by mkkot (mkkot) - Saturday, 10 August 2013, 17:51 GMT
Last edited by Dave Reisner (falconindy) - Thursday, 15 August 2013, 17:48 GMT
Task Type Bug Report
Category General
Status Closed
Assigned To No-one
Architecture All
Severity Medium
Priority Normal
Reported Version 4.1.2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

The same mirror (tried many), pacman's default downloading engine (it slows down after about half minute):

torcs-data-1.3.4-1-any 121,8 MiB 311K/s 07:54 [#########-------------] 45%

XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u:

24% [+++++===> ] 69.217.604 1,25MB/s eta 2m 41s


What I have tried to figure out what is wrong:
- tried to download the package manually with wget - full speed
- tried to download the package manually with firefox - full speed
- checked netstat output to see if pacman and wget uses different port so there could be some QoS rule applied - but they both use 80 and the same server.
- checked if there is QoS on my router disabled
- pacman -Syy
- checked with another router
- checked on proof.ovh.net that my bandwith is actually 10Mb/s down
- ping -i 0.2 noc.gts.pl:
--- noc.gts.pl ping statistics ---
102 packets transmitted, 102 received, 0% packet loss, time 20262ms
rtt min/avg/max/mdev = 25.631/26.329/28.842/0.433 ms



Additional info:
* package version(s)
Pacman v4.1.2 - libalpm v8.0.2


Steps to reproduce:

pacman -S alienarena
pacman -S torcs
This task depends upon

Closed by  Dave Reisner (falconindy)
Thursday, 15 August 2013, 17:48 GMT
Reason for closing:  Fixed
Additional comments about closing:  curl 7.32.0
Comment by John (graysky) - Saturday, 10 August 2013, 21:50 GMT
I don't think wget or pacman have any upper limits for d/l speeds. It is either your isp throttling you or your mirror is slow. What does your d/l speed read on a site like: speedtest.net ? Also consider using powerpill in the AUR if you wish to have parallel pacman downloads. Amazingly fast in my experience.
Comment by mkkot (mkkot) - Saturday, 10 August 2013, 22:08 GMT
Thanks for your answer. It looked like pacman was very sensitive to other Internet traffic and lower the speed even if this traffic was very little or none. My mirror is not slow for sure, it's located over my ISP's network. And, as I said, both wget and pacman traffic is transfered over port 80, so how my ISP could priority first and throttle latter? I answered already the question about speedtest (proof.ovh.net). I pay for 10Mb down but I get 10,5Mb so I'm pretty happy with my cable.
Comment by Dave Reisner (falconindy) - Wednesday, 14 August 2013, 00:38 GMT
Try with the curl binary rather than wget. pacman doesn't implement its own downloader, it just reuses libcurl.

FWIW, I have no problems pulling down 5MB/s or more with pacman.
Comment by mkkot (mkkot) - Thursday, 15 August 2013, 13:03 GMT
Done tests with curl and I can confirm it's pacman's issue. What I did:

[root@linux mk]# curl -O http://mirror.chmuri.net/archmirror/community/os/x86_64/torcs-data-1.3.4-1-any.pkg.tar.xz

I got speed around 1MB/s (which is max for my connection). Then I opened speedtest with Firefox, it took more than half of my bandwith for testing the connection, then I closed speedtest page and curl's speed rised back to 1MB/s.

Then I run pacman -S torcs.

I got speed around 1MB/s but then it was enough to open a random site, even router's management panel (so even LAN activity affects the throughput) to lower pacman's speed to 200-300-500kB/s. It finally got back to 1MB/s but it took about minute after all other connection activities stopped.

I must say that it actually came back to 1MB/s because this mirror is really close to me. With other mirrors it was impossible to regain full speed.
Comment by Dave Reisner (falconindy) - Thursday, 15 August 2013, 13:16 GMT
And with curl 7.32.0? It's in [testing], but I'm moving it to [core].
Comment by mkkot (mkkot) - Thursday, 15 August 2013, 17:38 GMT
Uncommented testing:
[2013-08-15 19:28] [PACMAN] upgraded curl (7.31.0-1 -> 7.32.0-1)

Now the problem described above doesn't occur.
Comment by Dave Reisner (falconindy) - Thursday, 15 August 2013, 17:48 GMT
Related to upstream curl fixes in the progress callback being called too frequently, then. Closing.

Loading...