I'm curious if this is a bug... My code location container has this

RUN

line at the end:

CMD ["dagster", "api", "grpc", "-h", "0.0.0.0", "-p", "4000", "--max_workers", "3", "--module-name", "my_module"]

If I materialize all of the assets in a job, dagster spins up 3 workers to handle concurrent processing. However, once it is all complete, if I again materialize all of the assets in the job (as I was doing as part of testing), dagster only spins up 2 workers (which is default). Is that expected or should I be specifying

--max_workers

elsewhere, too?

Hey clay - the "max-workers" parameter there is referring to a number of threads on the grpc server, it's not directly related to dagster execution. It sounds like you may be looking for the 'max_concurrent' parameter here, which controls how many ops execute at once in a given run: https://docs.dagster.io/concepts/ops-jobs-graphs/job-execution#default-job-executor

ah, ok! Thanks!

max_concurrent will determine how many processes get spun up for a particular job. Where those processes are running will depend on which executor you pick

ok, thanks for clarifying!