Is there a way to lunch runs within the

code location

pod and not in a separate pod (e.g. from the

k8sRunLauncher

)? I was hoping to run steps directly within the initial user deployment container to avoid really long cold starts we get with separate jobs. It feels like the

runLauncher

config should allow something like that:

runLauncher:
  type: DefaultRunLauncher

But it doesn't...

It supports this. You just have to use

type: CustomRunLauncher

.

runLauncher:
  type: CustomRunLauncher
  customRunLauncher:
     module: dagster
     class: DefaultRunLauncher
     config: {}

See this previous discussion.

Ah great! Thanks a lot ❤️

Are you getting any improvement at all? there’s the container startup time, kubernetes pod allocation, etc that is required if you want isolations in your jobs. since you don’t want isolations, the

DefaultRunLauncher

will run the job directly in your long standing code server. But if you are running multiple jobs in this code server, execution will get bogged down since your code server may not have enough resources to handle this simultaneous execution. I would start by beefing up your code server resources.

I'm only seeing some really minor improvement