Hey everyone.
A while back we had reports from folks particularly in Brno that operations to pagure.io were very slow. We put in place a workaround while we worked on the issue with network providers and tried various things. I'd like to know if any of those things have fixed (or at least made better) the issue.
So, if you had slow pagure connections in the past, can you:
* do some initial tests:
time git clone https://pagure.io/pagure.git
time curl https://pagure.io/pagure/issue/3714
time curl https://releases.pagure.org/virt-viewer/virt-viewer-x86-7.0.msi
* then add: 140.211.169.204 pagure.io or (if you use ipv6): 2605:bc80:3010:600:dead:beef:cafe:fed8 pagure.io
to your /etc/hosts file
* Then run the tests again:
time git clone https://pagure.io/pagure.git
time curl https://pagure.io/pagure/issue/3714
time curl https://releases.pagure.org/virt-viewer/virt-viewer-x86-7.0.msi
* Then remember to REMOVE the hosts entry so it's not there later causing you confusion.
Thanks in advance for any testing.
kevin
On Tue, Nov 13, 2018 at 05:20:28PM -0800, Kevin Fenzi wrote:
Hey everyone.
A while back we had reports from folks particularly in Brno that operations to pagure.io were very slow. We put in place a workaround while we worked on the issue with network providers and tried various things. I'd like to know if any of those things have fixed (or at least made better) the issue.
So, if you had slow pagure connections in the past, can you:
time git clone https://pagure.io/pagure.git time curl https://pagure.io/pagure/issue/3714 time curl https://releases.pagure.org/virt-viewer/virt-viewer-x86-7.0.msi
Hey,
I'm from Poland, which is close enough to Brno and far away from Pagure. Tests times are similar:
real 0m12.774s user 0m3.900s sys 0m0.881s
real 0m1.417s user 0m0.017s sys 0m0.012s
real 0m0.977s user 0m0.017s sys 0m0.007s
With forced DNS entries:
real 0m14.382s user 0m4.004s sys 0m0.856s
real 0m1.244s user 0m0.016s sys 0m0.008s
real 0m0.854s user 0m0.016s sys 0m0.007s
My network connection is residential, symmetrical 100MBps. As Fedora developer I've pagure.io cached in resolver probably, so the tests may not be relevant.
3.18user 0.70system 0:48.40elapsed 8%CPU (0avgtext+0avgdata 34732maxresident)k 0inputs+124568outputs (0major+10814minor)pagefaults 0swaps
0.01user 0.01system 0:01.67elapsed 1%CPU (0avgtext+0avgdata 10668maxresident)k 0inputs+0outputs (0major+752minor)pagefaults 0swaps
0.29user 0.31system 0:16.70elapsed 3%CPU (0avgtext+0avgdata 10804maxresident)k 0inputs+0outputs (0major+747minor)pagefaults 0swaps
→
3.11user 0.70system 0:10.40elapsed 36%CPU (0avgtext+0avgdata 34728maxresident)k 0inputs+124560outputs (0major+10734minor)pagefaults 0swaps
0.02user 0.00system 0:01.74elapsed 1%CPU (0avgtext+0avgdata 10608maxresident)k 0inputs+0outputs (0major+724minor)pagefaults 0swaps
0.25user 0.20system 0:13.51elapsed 3%CPU (0avgtext+0avgdata 10600maxresident)k 0inputs+0outputs (0major+749minor)pagefaults 0swaps On Wed, Nov 14, 2018 at 3:19 AM Kevin Fenzi kevin@scrye.com wrote:
Hey everyone.
A while back we had reports from folks particularly in Brno that operations to pagure.io were very slow. We put in place a workaround while we worked on the issue with network providers and tried various things. I'd like to know if any of those things have fixed (or at least made better) the issue.
So, if you had slow pagure connections in the past, can you:
- do some initial tests:
time git clone https://pagure.io/pagure.git
time curl https://pagure.io/pagure/issue/3714
time curl https://releases.pagure.org/virt-viewer/virt-viewer-x86-7.0.msi
- then add:
140.211.169.204 pagure.io or (if you use ipv6): 2605:bc80:3010:600:dead:beef:cafe:fed8 pagure.io
to your /etc/hosts file
- Then run the tests again:
time git clone https://pagure.io/pagure.git
time curl https://pagure.io/pagure/issue/3714
time curl https://releases.pagure.org/virt-viewer/virt-viewer-x86-7.0.msi
- Then remember to REMOVE the hosts entry so it's not there later
causing you confusion.
Thanks in advance for any testing.
kevin
infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro...
On Tue, Nov 13, 2018 at 05:20:28PM -0800, Kevin Fenzi wrote:
Hey everyone.
A while back we had reports from folks particularly in Brno that operations to pagure.io were very slow. We put in place a workaround while we worked on the issue with network providers and tried various things. I'd like to know if any of those things have fixed (or at least made better) the issue.
So, if you had slow pagure connections in the past, can you:
Not in Brno but I've seen it before
- do some initial tests:
time git clone https://pagure.io/pagure.git
$ time git clone https://pagure.io/pagure.git
Cloning into 'pagure'... remote: Counting objects: 47800, done. remote: Compressing objects: 100% (10562/10562), done. remote: Total 47800 (delta 37425), reused 47244 (delta 36945) Receiving objects: 100% (47800/47800), 23.15 MiB | 1.63 MiB/s, done. Resolving deltas: 100% (37425/37425), done. git clone https://pagure.io/pagure.git 5.08s user 1.10s system 32% cpu 18.866 total
time curl https://pagure.io/pagure/issue/3714
$ time curl https://pagure.io/pagure/issue/3714 -o /dev/null % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 40031 100 40031 0 0 13343 0 0:00:03 0:00:03 --:--:-- 11777 curl https://pagure.io/pagure/issue/3714 -o /dev/null 0.03s user 0.01s system 1% cpu 3.409 total
time curl https://releases.pagure.org/virt-viewer/virt-viewer-x86-7.0.msi
$ time curl https://releases.pagure.org/virt-viewer/virt-viewer-x86-7.0.msi -o /dev/null % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 52.9M 100 52.9M 0 0 60038 0 0:15:24 0:15:24 --:--:-- 88878 curl https://releases.pagure.org/virt-viewer/virt-viewer-x86-7.0.msi -o 0.95s user 1.84s system 0% cpu 15:24.42 total
Second attempt (after removing the line in /etc/hosts): $ time curl https://releases.pagure.org/virt-viewer/virt-viewer-x86-7.0.msi -o /dev/null % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 52.9M 100 52.9M 0 0 199k 0 0:04:31 0:04:31 --:--:-- 145k curl https://releases.pagure.org/virt-viewer/virt-viewer-x86-7.0.msi -o 0.84s user 1.01s system 0% cpu 4:31.53 total
- then add:
140.211.169.204 pagure.io to your /etc/hosts file
time git clone https://pagure.io/pagure.git
$ time git clone https://pagure.io/pagure.git Cloning into 'pagure'... remote: Counting objects: 47800, done. remote: Compressing objects: 100% (10562/10562), done. remote: Total 47800 (delta 37425), reused 47244 (delta 36945) Receiving objects: 100% (47800/47800), 23.15 MiB | 163.00 KiB/s, done. Resolving deltas: 100% (37425/37425), done. git clone https://pagure.io/pagure.git 6.12s user 1.75s system 5% cpu 2:29.54 total
Curious about the result, I tried a second time after running the commands below and the result is even worse :( $ time git clone https://pagure.io/pagure.git Cloning into 'pagure'... remote: Counting objects: 47800, done. remote: Compressing objects: 100% (10562/10562), done. remote: Total 47800 (delta 37425), reused 47244 (delta 36945) Receiving objects: 100% (47800/47800), 23.15 MiB | 89.00 KiB/s, done. Resolving deltas: 100% (37425/37425), done. git clone https://pagure.io/pagure.git 5.31s user 1.74s system 2% cpu 4:29.58 total
time curl https://pagure.io/pagure/issue/3714
$ time curl https://pagure.io/pagure/issue/3714 -o /dev/null % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 40031 100 40031 0 0 40031 0 0:00:01 0:00:01 --:--:-- 21464 curl https://pagure.io/pagure/issue/3714 -o /dev/null 0.02s user 0.01s system 1% cpu 1.878 total
time curl https://releases.pagure.org/virt-viewer/virt-viewer-x86-7.0.msi
$ time curl https://releases.pagure.org/virt-viewer/virt-viewer-x86-7.0.msi -o /dev/null % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 52.9M 100 52.9M 0 0 123k 0 0:07:17 0:07:17 --:--:-- 142k curl https://releases.pagure.org/virt-viewer/virt-viewer-x86-7.0.msi -o 1.21s user 2.06s system 0% cpu 7:17.54 total
Honestly, I'm not sure what to conclude from this.
Pierre
This is one where I do see a pretty big difference:
$ time curl https://pagure.io/static/vendor/emojione/emojione.sprites.png -o /dev/null % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 2408k 100 2408k 0 0 602k 0 0:00:04 0:00:04 --:--:-- 556k curl https://pagure.io/static/vendor/emojione/emojione.sprites.png -o 0.10s user 0.05s system 3% cpu 4.432 total
With the entry in /etc/hosts:
$ time curl https://pagure.io/static/vendor/emojione/emojione.sprites.png -o /dev/null % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 2408k 100 2408k 0 0 160k 0 0:00:15 0:00:15 --:--:-- 210k curl https://pagure.io/static/vendor/emojione/emojione.sprites.png -o 0.13s user 0.12s system 1% cpu 15.626 total
Pierre
Dne 14. 11. 18 v 2:20 Kevin Fenzi napsal(a):
So, if you had slow pagure connections in the past, can you:
- do some initial tests:
time git clone https://pagure.io/pagure.git
Tested from Brno RH office.
real 0m10,942s user 0m7,328s sys 0m1,965s
time curl https://pagure.io/pagure/issue/3714
real 0m1,443s user 0m0,090s sys 0m0,056s
time curl https://releases.pagure.org/virt-viewer/virt-viewer-x86-7.0.msi --output /tmp/f
real 2m7,566s user 0m0,585s sys 0m0,798s
- then add:
140.211.169.204 pagure.io
to your /etc/hosts file
Done.
- Then run the tests again:
time git clone https://pagure.io/pagure.git
real 4m35,394s user 0m8,759s sys 0m2,677s
time curl https://pagure.io/pagure/issue/3714
real 0m1,506s user 0m0,059s sys 0m0,030s
time curl https://releases.pagure.org/virt-viewer/virt-viewer-x86-7.0.msi --output /tmp/f
real 8m12,493s user 0m0,854s sys 0m1,296s
Miroslav
infrastructure@lists.fedoraproject.org
-
Igor Gnatenko -
Kevin Fenzi -
Miroslav Suchý -
Pierre-Yves Chibon -
Tomasz Torcz