are there any downsides to using the dask executor? I’m curious why the
DaskLocalExecutor
isn’t the default executor, if dask is a dep of prefect anyways.
k
Kevin Kho
07/06/2021, 9:56 PM
Hey, the answer is to have the defaults be the simplest. Similar to the spirit of this tweet.
w
wiretrack
07/06/2021, 10:22 PM
Also, I think you have to spin up a local dask cluster (the scheduler and the workers) to be able to use dask locally, while the local executor should run a thread or something (simple, easy), but I’m not too sure really
k
Kevin Kho
07/06/2021, 10:38 PM
I think the scheduler - worker is when you bring in dask and distributed. The LocalDaskExecutor is a multiprocessing pool.
w
wiretrack
07/06/2021, 10:49 PM
Hmmm, I thought I had the worker alive when I used the local executor. But maybe you just need dask installed.
Local: An executor that runs all functions locally using dask and a configurable dask scheduler.
Dask: An executor that runs all functions using the dask.distributed scheduler.
k
Kevin Kho
07/06/2021, 10:57 PM
Ah I see. Yeah you’re right
z
Zach Schumacher
07/06/2021, 11:17 PM
The local dask executor works for me without a dask cluster
w
wiretrack
07/06/2021, 11:18 PM
So probably I was just over complicating the execution really.
Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.