eric-valente

Would love some additional color here. Minute backtests are very, very slow. I do not need all the summary statistics - would love a way to filter which calculations I...

@Thomas214 Thanks for this - it did not seem to speed things up for me. Are you still using context.asset all in the backtest?

The only way I got things to work currently was to add security=False to the EC2Cluster instantiation, this removes the massive TLS strings for security and brings the size to...

any progress here?

Hi @jacobtomlinson Tried it with packages and no luck. The workers will turn on in EC2 and won't connect to the scheduler and then proceed to die. When I remove...

@jacobtomlinson This error then worker dies:  Here are my settings:  Note, this works if i simply remove nprocs from the worker_options. Thanks for your help!

Thanks again for your help here @jacobtomlinson Tried setting the worker class to Nanny but still same issue:  

https://github.com/dask/distributed/issues/4640 seems maybe related

Seems dask.distributed.Nanny does not accept nprocs either https://distributed.dask.org/en/latest/_modules/distributed/nanny.html#Nanny Fails with above init error: --spec '{"cls": "dask.distributed.Nanny", "opts": {"nprocs": 4, "name": "dask-4ffc56fd-worker-dd6509e3"}}' Works: --spec '{"cls": "dask.distributed.Nanny", "opts": {"ncores": 4, "name": "dask-4ffc56fd-worker-dd6509e3"}}'

Seems like the cloud-init to add a worker uses this style of starting a worker: python -m distributed.cli.dask_spec tcp://x.x.x.x:8786 --spec {"cls": "distributed.nanny.Nanny", "opts": {"nprocs": 4, "name": "dask-4ffc56fd-worker-dd6509e3"}} vs. this style:...