Uploaded image for project: 'SR for Bitbucket - Development'
  1. SR for Bitbucket - Development
  2. SRBITB-269

Getting changes and commits can cause performance problems

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Done
    • Priority: High
    • Resolution: Obsolete
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None
    • Sprint:
      Sprint 41, Sprint 42, Sprint 43, Sprint 44, Sprint 45, Sprint 46, Sprint 47, Sprint 48
    • Critical Points:
      0

      Description

      We should replace places we do Git operations using the PagedIterable with the new hooks API commit callback. There are two problems:

      • We filter the¬†PagedIterable which loads the items into memory.
      • Internally¬†you can't paginate in Git so we use more resources by not streaming.

      We can do this now because Bitbucket 5 contains the committer as well as the author when we read the commits, so we don't have to manually call git rev-list ourselves.

      We should use the new hooks API to get Bitbucket Server to provide us with the commits in the most efficient way.

      This should only be done for built-in pre and post hooks for now.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              szaporozhtsev Sergey Zaporozhtsev [X] (Inactive)
              Reporter:
              amarkham Adam Markham
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: