Hi,
Pagure.io is so slow for me to that point that I simple can't open ticket to report it. IOW, I am trying to load https://pagure.io/fedora-infrastructure/issues in my browser and it does not work, it just waits for response :/
~~~
$ curl https://pagure.io/fedora-infrastructure/issues -o /dev/null % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 107k 100 107k 0 0 30755 0 0:00:03 0:00:03 --:--:-- 30764
$ traceroute pagure.io traceroute to pagure.io (152.19.134.147), 30 hops max, 60 byte packets 1 _gateway (192.168.0.1) 3.274 ms 4.385 ms 4.320 ms 2 * * * 3 ip-86-49-1-161.net.upcbroadband.cz (86.49.1.161) 22.197 ms 22.094 ms 22.066 ms 4 cz-brn-pop40-ra2-vla2191.net.upc.cz (84.116.220.246) 121.057 ms 124.204 ms 124.182 ms 5 cz-brn-pop40-ra1-vla2110.net.upc.cz (84.116.221.41) 126.583 ms 126.456 ms 126.449 ms 6 cz-prg01a-ra4-vla2109.net.upc.cz (84.116.221.37) 126.402 ms 111.096 ms 116.115 ms 7 de-fra04a-rc1-ae33-0.aorta.net (84.116.135.5) 110.803 ms 137.982 ms 137.875 ms 8 de-fra04d-rc1-ae26-0.aorta.net (84.116.138.238) 137.842 ms 137.777 ms 137.724 ms 9 * * * 10 us-nyc01b-rd2-ae9-0.aorta.net (84.116.140.170) 138.336 ms 138.298 ms 115.267 ms 11 us-nyc01b-ri2-ae3-0.aorta.net (84.116.137.194) 114.465 ms 112.698 ms 110.019 ms 12 nyc2-brdr-01.inet.qwest.net (63.235.40.165) 136.127 ms 136.117 ms 136.086 ms 13 dca-edge-23.inet.qwest.net (67.14.6.158) 159.519 ms 159.547 ms 161.527 ms 14 65.120.78.78 (65.120.78.78) 136.700 ms 135.992 ms 135.886 ms 15 uncmanning-to-rtp-ip-asr-gw.ncren.net (128.109.19.90) 132.844 ms 137.504 ms 136.760 ms 16 core-m-v1214.net.unc.edu (152.19.255.66) 135.283 ms 136.117 ms 138.533 ms 17 152.19.255.70 (152.19.255.70) 128.737 ms 128.655 ms 128.518 ms 18 152.19.255.166 (152.19.255.166) 147.476 ms 132.950 ms 137.336 ms 19 vmhost1-rsa.fedora.ibiblio.org (152.19.134.147) 126.626 ms !X 130.794 ms !X 121.215 ms !X ~~~
The strange thing is that the pagure title page or the project overview can be loaded just fine and neither the tools above shows any suspicious behavior to me.
Vít
On Fri, May 04, 2018 at 04:29:20PM +0200, Vít Ondruch wrote:
Hi,
Pagure.io is so slow for me to that point that I simple can't open ticket to report it. IOW, I am trying to load https://pagure.io/fedora-infrastructure/issues in my browser and it does not work, it just waits for response :/
Just basic ideas/questions: Do you have some plugins/extensions installed in your browser? Did you try in private browsing mode or with a clean profile? If you try from another location (home, coffee shop) do you see the same slowness?
Pierre
Dne 4.5.2018 v 16:34 Pierre-Yves Chibon napsal(a):
On Fri, May 04, 2018 at 04:29:20PM +0200, Vít Ondruch wrote:
Hi,
Pagure.io is so slow for me to that point that I simple can't open ticket to report it. IOW, I am trying to load https://pagure.io/fedora-infrastructure/issues in my browser and it does not work, it just waits for response :/
Just basic ideas/questions: Do you have some plugins/extensions installed in your browser?
I have some, but I don't think I have anything special. I definitely don't have any addblocker or so.
Did you try in private browsing mode
Actually trying with private mode now. I got to https://id.fedoraproject.org but the redirect back to pagure does not work ...
or with a clean profile? If you try from another location (home, coffee shop) do you see the same slowness?
Working from home. But I don't remember to have such issues.
V.
Pierre _______________________________________________ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org
I removed cookies and the page can be loaded just fine, but it appears I can't login now ...
Vít
Dne 4.5.2018 v 16:29 Vít Ondruch napsal(a):
Hi,
Pagure.io is so slow for me to that point that I simple can't open ticket to report it. IOW, I am trying to load https://pagure.io/fedora-infrastructure/issues in my browser and it does not work, it just waits for response :/
$ curl https://pagure.io/fedora-infrastructure/issues -o /dev/null % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 107k 100 107k 0 0 30755 0 0:00:03 0:00:03 --:--:-- 30764 $ traceroute pagure.io traceroute to pagure.io (152.19.134.147), 30 hops max, 60 byte packets 1 _gateway (192.168.0.1) 3.274 ms 4.385 ms 4.320 ms 2 * * * 3 ip-86-49-1-161.net.upcbroadband.cz (86.49.1.161) 22.197 ms 22.094 ms 22.066 ms 4 cz-brn-pop40-ra2-vla2191.net.upc.cz (84.116.220.246) 121.057 ms 124.204 ms 124.182 ms 5 cz-brn-pop40-ra1-vla2110.net.upc.cz (84.116.221.41) 126.583 ms 126.456 ms 126.449 ms 6 cz-prg01a-ra4-vla2109.net.upc.cz (84.116.221.37) 126.402 ms 111.096 ms 116.115 ms 7 de-fra04a-rc1-ae33-0.aorta.net (84.116.135.5) 110.803 ms 137.982 ms 137.875 ms 8 de-fra04d-rc1-ae26-0.aorta.net (84.116.138.238) 137.842 ms 137.777 ms 137.724 ms 9 * * * 10 us-nyc01b-rd2-ae9-0.aorta.net (84.116.140.170) 138.336 ms 138.298 ms 115.267 ms 11 us-nyc01b-ri2-ae3-0.aorta.net (84.116.137.194) 114.465 ms 112.698 ms 110.019 ms 12 nyc2-brdr-01.inet.qwest.net (63.235.40.165) 136.127 ms 136.117 ms 136.086 ms 13 dca-edge-23.inet.qwest.net (67.14.6.158) 159.519 ms 159.547 ms 161.527 ms 14 65.120.78.78 (65.120.78.78) 136.700 ms 135.992 ms 135.886 ms 15 uncmanning-to-rtp-ip-asr-gw.ncren.net (128.109.19.90) 132.844 ms 137.504 ms 136.760 ms 16 core-m-v1214.net.unc.edu (152.19.255.66) 135.283 ms 136.117 ms 138.533 ms 17 152.19.255.70 (152.19.255.70) 128.737 ms 128.655 ms 128.518 ms 18 152.19.255.166 (152.19.255.166) 147.476 ms 132.950 ms 137.336 ms 19 vmhost1-rsa.fedora.ibiblio.org (152.19.134.147) 126.626 ms !X 130.794 ms !X 121.215 ms !X
The strange thing is that the pagure title page or the project overview can be loaded just fine and neither the tools above shows any suspicious behavior to me.
Vít
infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org
If I go to pagure.io/login, I can get logged in, but then I can't access the issues again ...
V.
Dne 4.5.2018 v 16:34 Vít Ondruch napsal(a):
I removed cookies and the page can be loaded just fine, but it appears I can't login now ...
Vít
Dne 4.5.2018 v 16:29 Vít Ondruch napsal(a):
Hi,
Pagure.io is so slow for me to that point that I simple can't open ticket to report it. IOW, I am trying to load https://pagure.io/fedora-infrastructure/issues in my browser and it does not work, it just waits for response :/
$ curl https://pagure.io/fedora-infrastructure/issues -o /dev/null % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 107k 100 107k 0 0 30755 0 0:00:03 0:00:03 --:--:-- 30764 $ traceroute pagure.io traceroute to pagure.io (152.19.134.147), 30 hops max, 60 byte packets 1 _gateway (192.168.0.1) 3.274 ms 4.385 ms 4.320 ms 2 * * * 3 ip-86-49-1-161.net.upcbroadband.cz (86.49.1.161) 22.197 ms 22.094 ms 22.066 ms 4 cz-brn-pop40-ra2-vla2191.net.upc.cz (84.116.220.246) 121.057 ms 124.204 ms 124.182 ms 5 cz-brn-pop40-ra1-vla2110.net.upc.cz (84.116.221.41) 126.583 ms 126.456 ms 126.449 ms 6 cz-prg01a-ra4-vla2109.net.upc.cz (84.116.221.37) 126.402 ms 111.096 ms 116.115 ms 7 de-fra04a-rc1-ae33-0.aorta.net (84.116.135.5) 110.803 ms 137.982 ms 137.875 ms 8 de-fra04d-rc1-ae26-0.aorta.net (84.116.138.238) 137.842 ms 137.777 ms 137.724 ms 9 * * * 10 us-nyc01b-rd2-ae9-0.aorta.net (84.116.140.170) 138.336 ms 138.298 ms 115.267 ms 11 us-nyc01b-ri2-ae3-0.aorta.net (84.116.137.194) 114.465 ms 112.698 ms 110.019 ms 12 nyc2-brdr-01.inet.qwest.net (63.235.40.165) 136.127 ms 136.117 ms 136.086 ms 13 dca-edge-23.inet.qwest.net (67.14.6.158) 159.519 ms 159.547 ms 161.527 ms 14 65.120.78.78 (65.120.78.78) 136.700 ms 135.992 ms 135.886 ms 15 uncmanning-to-rtp-ip-asr-gw.ncren.net (128.109.19.90) 132.844 ms 137.504 ms 136.760 ms 16 core-m-v1214.net.unc.edu (152.19.255.66) 135.283 ms 136.117 ms 138.533 ms 17 152.19.255.70 (152.19.255.70) 128.737 ms 128.655 ms 128.518 ms 18 152.19.255.166 (152.19.255.166) 147.476 ms 132.950 ms 137.336 ms 19 vmhost1-rsa.fedora.ibiblio.org (152.19.134.147) 126.626 ms !X 130.794 ms !X 121.215 ms !X
The strange thing is that the pagure title page or the project overview can be loaded just fine and neither the tools above shows any suspicious behavior to me.
Vít
infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org
infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org
On Fri, May 4, 2018 at 4:36 PM, Vít Ondruch vondruch@redhat.com wrote:
If I go to pagure.io/login, I can get logged in, but then I can't access the issues again ...
I had those same exact issues yesterday immediatelly after new pagure release. When logged out I could access https://pagure.io/fedora- infrastructure/issues, I logged out and could no longer access it.
clime
V.
Dne 4.5.2018 v 16:34 Vít Ondruch napsal(a):
I removed cookies and the page can be loaded just fine, but it appears I can't login now ...
Vít
Dne 4.5.2018 v 16:29 Vít Ondruch napsal(a):
Hi,
Pagure.io is so slow for me to that point that I simple can't open ticket to report it. IOW, I am trying to load https://pagure.io/fedora-infrastructure/issues in my browser and it
does
not work, it just waits for response :/
$ curl https://pagure.io/fedora-infrastructure/issues -o /dev/null % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 107k 100 107k 0 0 30755 0 0:00:03 0:00:03 --:--:-- 30764 $ traceroute pagure.io traceroute to pagure.io (152.19.134.147), 30 hops max, 60 byte packets 1 _gateway (192.168.0.1) 3.274 ms 4.385 ms 4.320 ms 2 * * * 3 ip-86-49-1-161.net.upcbroadband.cz (86.49.1.161) 22.197 ms 22.094 ms 22.066 ms 4 cz-brn-pop40-ra2-vla2191.net.upc.cz (84.116.220.246) 121.057 ms 124.204 ms 124.182 ms 5 cz-brn-pop40-ra1-vla2110.net.upc.cz (84.116.221.41) 126.583 ms 126.456 ms 126.449 ms 6 cz-prg01a-ra4-vla2109.net.upc.cz (84.116.221.37) 126.402 ms 111.096 ms 116.115 ms 7 de-fra04a-rc1-ae33-0.aorta.net (84.116.135.5) 110.803 ms 137.982 ms 137.875 ms 8 de-fra04d-rc1-ae26-0.aorta.net (84.116.138.238) 137.842 ms
137.777
ms 137.724 ms 9 * * * 10 us-nyc01b-rd2-ae9-0.aorta.net (84.116.140.170) 138.336 ms 138.298 ms 115.267 ms 11 us-nyc01b-ri2-ae3-0.aorta.net (84.116.137.194) 114.465 ms 112.698 ms 110.019 ms 12 nyc2-brdr-01.inet.qwest.net (63.235.40.165) 136.127 ms 136.117
ms
136.086 ms 13 dca-edge-23.inet.qwest.net (67.14.6.158) 159.519 ms 159.547 ms 161.527 ms 14 65.120.78.78 (65.120.78.78) 136.700 ms 135.992 ms 135.886 ms 15 uncmanning-to-rtp-ip-asr-gw.ncren.net (128.109.19.90) 132.844 ms 137.504 ms 136.760 ms 16 core-m-v1214.net.unc.edu (152.19.255.66) 135.283 ms 136.117 ms 138.533 ms 17 152.19.255.70 (152.19.255.70) 128.737 ms 128.655 ms 128.518 ms 18 152.19.255.166 (152.19.255.166) 147.476 ms 132.950 ms 137.336 ms 19 vmhost1-rsa.fedora.ibiblio.org (152.19.134.147) 126.626 ms !X 130.794 ms !X 121.215 ms !X
The strange thing is that the pagure title page or the project overview can be loaded just fine and neither the tools above shows any suspicious behavior to me. Vít _______________________________________________ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists.
fedoraproject.org
infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists.
fedoraproject.org _______________________________________________ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists. fedoraproject.org
It is the same with pagure itself - https://pagure.io/pagure/issue/3207
DB is missing indexes? Or there is some loop in Pagure that goes slow because of number of issues? How to profile it?
Anatoli Babenia wrote:
It is the same with pagure itself - https://pagure.io/pagure/issue/3207
DB is missing indexes? Or there is some loop in Pagure that goes slow because of number of issues? How to profile it?
It was something like that. With many thanks to Patrick, this issue should be largely fixed now. What took close to 10 minutes to load (if you were patient enough to let it go that long) now takes closer to 5 seconds.
If that's not the case for anyone who was experiencing this, please reply.
Thanks again to Patrick for digging into this.
Dne 7.5.2018 v 21:17 Todd Zullinger napsal(a):
Anatoli Babenia wrote:
It is the same with pagure itself - https://pagure.io/pagure/issue/3207
DB is missing indexes? Or there is some loop in Pagure that goes slow because of number of issues? How to profile it?
It was something like that. With many thanks to Patrick, this issue should be largely fixed now. What took close to 10 minutes to load (if you were patient enough to let it go that long) now takes closer to 5 seconds.
If that's not the case for anyone who was experiencing this, please reply.
Thanks again to Patrick for digging into this.
First load of [1] took like 15s for me, but the second try took approximately 2,5s. The issue list of pagure [2] loaded in reasonable time. So whatever was the fix, it looks promising.
V.
[1] https://pagure.io/releng/issues [2] https://pagure.io/pagure/issues
infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org
infrastructure@lists.fedoraproject.org