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@xxxxxxxxx> 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@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx > 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@xxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxxxx
