#2710 Forking a repo very slow
Closed: Duplicate 6 years ago Opened 6 years ago by bex.

I realize that we have some timing and resource challenges with Pagure. Is it possible to have someone break out a series of easyfix style tasks that would allow us to get performance improvements on forking? this is part of the onboarding of a contributor and is a stumbling block.


The forking itself is/should be really quick what is slow is re-generating the ACLs on the backend and that's not an easyfix (and also highly depending on how many people are using the server at that time for example (ie how busy the workers are).

Can we get more workers? I appear to always be hitting busy times :)

We have this ticket https://pagure.io/fedora-infrastructure/issue/6441 to add monitoring to the workers so we can make an educated decision on whether we need more workers or not.

Note that there is always only one worker refreshing the ACLs on the backend to avoid multiple processes writing on each other. So more workers will make the fork come back quicker on screen but not the banner that ACLs are being refreshed go away more quickly.

ok - thank you. I am going to close this is as a duplicate.

Metadata Update from @bex:
- Issue close_status updated to: Duplicate
- Issue status updated to: Closed (was: Open)

6 years ago

Thanks :)

Also, we're working with upstream gitolite to try to speed things up (though in this case he already gave us a couple of proposals and we've been the ones lacking time to implement/test them :s)

Login to comment on this ticket.

Metadata