In current implementation SubtaskExecutionActor.run_subtask keeps the whole lifecycle of a subtask. This disables the possibility to submit subtasks in batches, which is a major time cost of supervisors. As all calls of SchedulingAPI.finish_subtasks own SubtaskResult already, it is possible to make run_subtask to start subtasks only and stops tracking subtask execution.
In current implementation
SubtaskExecutionActor.run_subtaskkeeps the whole lifecycle of a subtask. This disables the possibility to submit subtasks in batches, which is a major time cost of supervisors. As all calls ofSchedulingAPI.finish_subtasksownSubtaskResultalready, it is possible to makerun_subtaskto start subtasks only and stops tracking subtask execution.