Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Merge requests
  • !214

Merged
Created Dec 16, 2011 by Administrator@rootOwner

Project destroy relationship speed fix

  • Overview 0
  • Commits 1
  • Changes 1

Created by: mutewinter

Removes destroy callback for UsersProjects when a project is destroyed. Previously, the after_destroy hook for UsersProjects would be called for every user on the project, causing a delay of about 2 seconds per user when destroying a project.

This works because the gitolite config will be updated at at the end to remove the entry entirely, thereby removing the users anyway.

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: github/fork/mutewinter/project_destroy_speed_fix