Look at historypoint optimizations.

XMLWordPrintable

    • Type: Suggestion
    • Resolution: Fixed
    • 2.4
    • Component/s: Reporting
    • None

      When generating a historypoint, the entire per-test coverage is loaded:
      ie: collateSlicePairs .

      This is rather expensive on very large projects, and is not used in the historypoint xml, nor the historyreport.

      Consider not calling collateSlicePairs when generating a historypoint.

      see attached thread dump:

      Also look at the possibility for a non-source level only historypoint, if this is not already the case.

        1. clover.jar
          9.12 MB
          Nick
        2. historypoint-stacks.txt
          12 kB
          Nick

            Assignee:
            Unassigned
            Reporter:
            Nick
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: