Hey guys, looking at the docs I wasn't able to und...
# announcements
a
Hey guys, looking at the docs I wasn't able to understand the different between
dagit.execution_manager.disabled.max_concurrent_runs
set in dagster.yaml and
execution.multiprocess.config.max_concurrent
. And kind of related: I would like to have multi-threaded solid runs rather than multi-process runs, is that achievable?
a
the dagit
execution_manager
has been removed, we have to clean up that section of the docs For the latter, the multiprocess executor executes each step it its own isolated process. The
max_concurrent
just bounds how many simultaneous step subprocess can exist at a time.
I would like to have multi-threaded solid runs rather than multi-process runs, is that achievable?
We haven’t written that executor yet, but theoretically you could.
If you want to file an issue for the multi-threaded executor and explain your use case or why it is desirable that would be useful context for us to have
a
Thanks for the reply Alex. I'll try to make the case for a multi-threaded executor in an issue sometime this week.