Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • G gitlab-ce
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • nexedinexedi
  • gitlab-ce
  • Repository
  • gitlab-ce
  • app
  • models
  • merge_request_diff.rb
Find file BlameHistoryPermalink
  • Stan Hu's avatar
    Optimize merge request refresh by using the database to check commit SHAs · dbc03ce3
    Stan Hu authored Nov 02, 2018
    Previously for a given merge request, we would:
    
    1. Create the array of commit SHAs involved in the push (A)
    2. Request all merge request commits and map the SHA (B)
    3. Reload the diff if there were any common commits between A and B
    
    We can avoid additional database querying and overhead by
    checking with the database whether the merge request contains any
    of the commit SHAs.
    
    Relates to https://gitlab.com/gitlab-org/gitlab-ce/issues/53213
    dbc03ce3
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7