Performance regression for perforce indexing from 2.9 to 3.4

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Medium
    • 3.6.0
    • Affects Version/s: 3.1.0, 3.5.2
    • Component/s: None
    • None

      Despite some time spent bisecting the Fisheye source tree I haven't been able to identify the exact commit that is responsible, but I have identified that this issue was first introduced in Fisheye 3.1.

      The problem

      The P4Scanner.indexRevisions method builds up a list of changesets until the list is larger than the batch size. It then passes them off to the indexBatch() method. Since 3.1 the list is not cleared after the batch is indexed and so all changesets that have been indexed so far are re-passed to the indexBatch method

              Assignee:
              Richard Stephens (Inactive)
              Reporter:
              Richard Stephens (Inactive)
              Votes:
              6 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - Not Specified
                  Not Specified
                  Logged:
                  Time Spent - 0.15h
                  0.15h