Hello, I am investigating a very weird issue with GitLab CE 8.1.4 Briefly, project forking is taking a *huge *amount of time, far in excess of any reasonable expectation. Example: a 40 MB project took nearly *an hour *to fork.
Here is what I found so far: - CPU, Memory and Disk all appear to be fine - so I don't believe there is any resource contention issue. - The database (dedicated MySQL instance) resides on a separate server, but again there is no indication of any significant traffic. - Cloning the same project to my desktop took only *seconds *to complete. Since fork is really just a server-side clone, they should both take about the same amount of time, no? - The fork process does complete successfully. - I believe this issue is relatively new - we've been using GitLab CE for a few months now and I'm pretty sure my users that do forks only saw this behavior recently. Unfortunately I don't know which GitLab release is involved - we went from 7.x to 8.0.4 to 8.1.4, so it's probably one of the 8.x releases. - gitlab-rake check said everything is good. One of my theories is that this is actually a *sidekiq *problem, since I understand that *sidekiq *is what is actually running the fork task. I'm going to try rebooting the server VM next (when in doubt, reboot! ;-)). I am hoping someone here might have seen this before. Thank you in advance for your input, Michael -- You received this message because you are subscribed to the Google Groups "GitLab" group. To unsubscribe from this group and stop receiving emails from it, send an email to gitlabhq+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/gitlabhq/a78258e2-5bea-4a57-b1ef-230001e857a0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
