DevHeads.net

Scratch build uploads to koji VERY SLOW

Is anyone else experiencing this? I did a speed test on my Xfinity and it
doesn't appear to be on my end.

I'm getting about 100-200kB/s uploads... On larger projects that's very
painful.

Thanks,
Richard

Comments

Re: Scratch build uploads to koji VERY SLOW

By Christian Dersch at 03/04/2019 - 13:36

On 3/4/19 6:32 PM, Richard Shaw wrote:
Yes, same here.

Greetings,
Christian

Re: Scratch build uploads to koji VERY SLOW

By Kevin Fenzi at 03/06/2019 - 19:36

On 3/4/19 9:36 AM, Christian Dersch wrote:
Well, sadly we don't run the internet, so there's not much we can do if
it's just network related. ;(

Has it always been like this for you, or is it a new change?

Nothing I can think of has changed recently on the pkgs end...

kevin

Re: Scratch build uploads to koji VERY SLOW

By Richard Shaw at 03/06/2019 - 20:14

New since the last couple of weeks but I've been more active working on
FTBFS issues so can't say exactly when it started. It's never been super
speedy but also never been this painful.

Thanks,
Richard

Re: Scratch build uploads to koji VERY SLOW

By Kevin Fenzi at 03/06/2019 - 20:38

On 3/6/19 4:14 PM, Richard Shaw wrote:
Odd. I can't think of anything on the server end that has changed
recently that might cause this. It's just as fast as always for me.

Has curl been updated on your machine(s) around the time it started?

Does koji --debug build scratch tag src.rpm

give you any output?

Re: Scratch build uploads to koji VERY SLOW

By Richard Shaw at 03/07/2019 - 14:08

Hah... just tried it and the srpm uploaded at >1MB/sec...

Thanks,
RIchard

Re: Scratch build uploads to koji VERY SLOW

By Ken Dreyer at 03/08/2019 - 13:00

I guess this depends on the status of the Apache httpd workers. Like are
they stuck in IO to the /mnt/koji scratch location, or something else?

Unfortunately it's not secure to publicly display Koji's in-flight HTTP
requests with mod_status, since the URLs contain the authenticated session
information, but that's where I'd go for the next level of investigation if
this happens frequently.

Maybe we need a separate utility in kojiweb to sanitize the hub's
mod_status' output for the public and display "what's the hub doing now".

- Ken