You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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 ofSchedulingAPI.finish_subtasks
ownSubtaskResult
already, it is possible to makerun_subtask
to start subtasks only and stops tracking subtask execution.The text was updated successfully, but these errors were encountered: