[midPoint-git] [Evolveum/midpoint] aa5210: Stop collecting executions for aggregating tasks

[mederly]

  Branch: refs/heads/master
  Home:   https://github.com/Evolveum/midpoint
  Commit: aa52109d707107ada4ae579471efe41ffdf75da5
      https://github.com/Evolveum/midpoint/commit/aa52109d707107ada4ae579471efe41ffdf75da5
  Author: Pavol Mederly <mederly at evolveum.com>
  Date:   2021-03-23 (Tue, 23 Mar 2021)

  Changed paths:
    M infra/schema/src/main/java/com/evolveum/midpoint/schema/statistics/IterativeOperationCollector.java
    M infra/schema/src/main/java/com/evolveum/midpoint/schema/statistics/IterativeTaskInformation.java
    M infra/schema/src/main/java/com/evolveum/midpoint/schema/util/task/TaskOperationStatsUtil.java
    M infra/schema/src/main/java/com/evolveum/midpoint/schema/util/task/TaskPartPerformanceInformation.java
    M repo/repo-common/src/main/java/com/evolveum/midpoint/repo/common/task/AbstractIterativeTaskPartExecution.java
    M repo/repo-common/src/main/java/com/evolveum/midpoint/repo/common/task/ProcessingCoordinator.java
    M repo/repo-common/src/main/java/com/evolveum/midpoint/repo/common/task/TaskReportingOptions.java
    M repo/task-api/src/main/java/com/evolveum/midpoint/task/api/StatisticsCollectionStrategy.java
    M repo/task-api/src/main/java/com/evolveum/midpoint/task/api/test/NullTaskImpl.java
    M repo/task-quartz-impl/src/main/java/com/evolveum/midpoint/task/quartzimpl/TaskQuartzImpl.java
    M repo/task-quartz-impl/src/main/java/com/evolveum/midpoint/task/quartzimpl/statistics/Statistics.java
    M repo/task-quartz-impl/src/test/java/com/evolveum/midpoint/task/quartzimpl/MockParallelTaskHandler.java

  Log Message:
  -----------
  Stop collecting executions for aggregating tasks

In order to compute wall clock time average and throughput, tasks
collect information about when they were started and stopped.
Normally this is not a problem, because any task is suspended/resumed
(presumably) only a few times until finished.

But tasks that aggregate statistics - like livesync, async update,
or scanners - gradually grow very large. Because there's no time
to implement a reasonable solution for this before 4.3 release,
we simply turned off computation of wall clock time related statistics
for these tasks.