Hi Tomas, I think the combined run launcher is worth trying for your use case, but does have some caveats. We actually launched something very similar to that in Dagster Cloud Serverless, where we have more chance to monitor how things are working. We found
• much lower run start time (just wait for process init, don’t have to wait for a new container)
• but, it’s easy to OOM the standing gRPC server. As a result, we increased Memory from 256mb for the standing server to 1gb. We also introduced a default limit of 1 concurrent run on the standing server, and any other runs we launch with an isolated container.