Destroying projects often times out
Created by: bendavies
When destroying projects, our installation of gitlab often times out.
I'm guessing this is due to the multiple dependent: :destroy on Project.
The project destroys that our timing out for us happen to have 30+ users assigned, so i guess that is where the performance issue is?
I'm not a ruby dev, so apologies if the diagnosis is way off!
Activity
Created by: bendavies
It looks like to me that https://github.com/gitlabhq/gitlabhq/blob/master/app/models/users_project.rb#L15 is the performance bottle neck. i.e updating the repository is slow, and doing so every time a user_project is deleted is just not going to work.
This task could be moved off to the queue?
By Administrator on 2012-08-29T10:42:09 (imported from GitLab project)
By Administrator on 2012-08-29T10:42:09 (imported from GitLab)
Created by: stevenwcarter
+1 on moving this off to the queue. I was about to open an issue suggesting that. Same with adding users to a repository. Doing a team import from another project runs into the same issue.
By Administrator on 2012-11-29T21:56:24 (imported from GitLab project)
By Administrator on 2012-11-29T21:56:24 (imported from GitLab)
