What is the pros/cons of using Futures/Delayed?

[scharlottej13]

Hi @bcaglaraydin and welcome!

This is a hard question to answer without knowing more about what how you’d like to use Dask. Mind sharing a bit more about what you’d like to do and how you’re deploying Dask (e.g. locally, HPC cluster, in the cloud)?

In addition to the Dask documentation on the Delayed and Futures APIs, this explanation from Ian Rose might help:

Documentation on the interplay between graphs and futures

Hi @akhmerov, welcome! I agree that the documentation around distributed.Futures is pretty confusing, and it should be improved. To me, the important differences (and I’m editorializing a bit here) are: Futures are mostly a reimplementation of the concurrent.futures API. It’s mostly a different API from the dask collections API (e.g., dask.dataframe or dask.array). Futures represent an unrealized result on a distributed cluster. They are defined in distributed, and almost entirely absent fr…