Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-19481

Improve refs resolution performance

XMLWordPrintable

    • 8
    • We collect Bitbucket feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.
    • CtB - Improve Existing

      Summary

      Improve Git references resolution performance by optimising the file operations involved in the background.

      Changes implemented as part of this ticket

      Resolving of refs to commit IDs is now improved for heavy fork based workflows

      This operation can now utilize multiple threads. There is a new config property that defines how many threads can be used for this operation:

      pullrequest.rescope.ref-resolve.max.threads=20
      

      Setting this property value to 0 will restore the original behavior.

      Applying the rescope result to pull requests is more optimized

      There was some unnecessary work performed when applying the rescope result to the Git repository on disk. This work has been optimized and rescope results will now be applied faster.

      Resolving refs to commit IDs is now faster on NFS

      The number of IO operations needed to resolve refs has been greatly reduced. The impact of this change is especially noticeable on NFS or when the directory tree is deeply nested.

            wkritzinger Wolfgang Kritzinger
            jmariano@atlassian.com JP Mariano
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: