• Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Mesh
    • None
    • 6
    • 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.

      In the initial (Bitbucket 8.0) release of Mesh fork synchronisation throughput when Mesh is used can be slower than a non-Mesh deployment. This gap should be reduced or eliminated such that Mesh is viable for instances that rely on a fork based workflow.

          Form Name

            [BSERV-13268] Mesh: Improve fork ref sync performance

            Are any updates available ?  In particular, is this still a concern at Bitbucket 8.9.19 (Mesh 2.0.33) ?  Thanks.

            Val Naipaul added a comment - Are any updates available ?  In particular, is this still a concern at Bitbucket 8.9.19 (Mesh 2.0.33) ?  Thanks.

              Unassigned Unassigned
              behumphreys Ben Humphreys
              Votes:
              9 Vote for this issue
              Watchers:
              12 Start watching this issue

                Created:
                Updated: