Closed szopal closed 3 months ago
There was an optimization for this in the 2.11.3. Please kick the tires there and see if it helps.
Thanks!
Yes, after passing a single element, the time decreased from 30 seconds to 15 seconds for 100 task definitions and 1300 task executions however, I am concerned that if the number of records in the TASK_EXECUTION table is very large, on the order of several hundred thousand, the problem may still occur.
In 2.11.2 I've noticed that getting list all task definition last very long. After analyze code, I think that I found reason - in class DefaultAggregateTaskExplorer:
TaskDefinitionController pass to getLatestTaskExecutionsByTaskNames all task definition as list - i.e. 100 definitions. But in method getLatestTaskExecutionsByTaskNames there is a loop where every element in a loop execute
but for whole list - not for one element:
taskExplorer.getLatestTaskExecutionsByTaskNames(taskNames) VS taskExplorer.getLatestTaskExecutionsByTaskNames(taskName)
Please, let me know if should be pass list or one element of list.