On Fri, Feb 14, 2020 at 06:21:34PM +0100, Marius Schwarz wrote:
Am 14.02.20 um 17:57 schrieb Kevin Fenzi:
> On Fri, Feb 14, 2020 at 08:07:19AM -0500, Stephen John Smoogen wrote:
>> On Fri, 14 Feb 2020 at 06:21, Leigh Griffin <lgriffin(a)redhat.com> wrote:
>>
>>>
>>> On Fri, Feb 14, 2020 at 12:59 AM Artem Tim <ego.cordatus(a)gmail.com>
wrote:
>>>
>>>> Same here. I am waiting several minutes for every my action. This is
very
>>>> unproductive.
>>>>
>>> Log it as a ticket and I can get the CPE folks to investigate it and see
>>> if there is an obvious problem that we can help with.
>>>
>>
>> for people having this issue the ticket is
>>
https://pagure.io/fedora-infrastructure/issue/8648
>>
>> We need an idea of the geolocation you are coming from, traceroutes of
>> where you are going from and if possible in the browser any links etc which
>> are showing very slow (aka in Firefox right click inspect, and switch to
>> the network page and do a ^R on the
koji.fedoraproject.org page)
> Also, it might help if people noted the exact time of day (UTC) they are
> accessing things?
>
> I suspect it may be backup slowness (which happens after 00:00UTC +-
> 2hour)
"NOW" aka. 14.2.2020 18:15 CET the same pagecall to koji and firefox
rpm download where as smooth as they could be.
ok. So that means the task link loaded in under 4 seconds?
But, the koji test page from the ticket, had 4,5 seconds loadtime, which
was the first page i visited in koji today.
Had before, but doesn't now? Or still does now?
I know this behaviour from my serverfarm, if the initial DNS resolver
is
not responding and the timeout until the second is asked, kicks in.
As the server does no longer need to ask for an ip resolv on the second
visit (here firefox), it responds faster.
You mean the end user dns? Sure, could cause problems indeed... but
thats out of our control.
This does not explain the worst case download rate from yesterday, but
it can explain the results people have writte to the ticket for visiting
koji .
It would seem odd for a variety of people to all hit dns issues at the
same time with different end user servers.
Anyhow, I have asked for more info in the ticket, hopefully we can
figure something out.
kevin