Guillaume Onfroy
03/16/2023, 1:58 PMK8sRunLauncher
: there seems to be such a huge cold start delay for the executor to actually run the content of job for each step. When the launcher provisions the job and the container starts, it takes ~2:30m to start the step (RUN_START
/ STEP_WORKING_STARTING
) and ~4:00m to actually start the execution (STEP_START
). Those numbers are consistent across all our jobs on k8s regardless of the resources allocated. Or those delays expected?