Parallel streams with buffers about streamz

[martindurant]

Streamz is not a parallelism framework, but it can be concurrent ("async") for tasks that spend most of their time waiting. If your functions were async and you used asyncio.wait, they would have a shorter total run time. However, whether you can actually get parallelism depends on exactly what calls you make, and mixing CPU with IO is always tricky. Often a separate worker thread would end up running CPU loads (but python's GIL means you still might not get parallelism).

Dask can well be the parallelism engine for you, and it has various cluster topologies you can set up. From streamz's point of view, dask is a handy way to hand of mini-batches of events; but it could also be long-running tasks like downloads, in theory. In fact, if download/process is all you are doing, you can just use dask without srteamz (the delayed or client.submit patterns).

Note that no one is developing streamz these days, but I believe it can do what you want, if you have the interest to dig in.

[john-jam]

@martindurant Thanks for your prompt and useful answer!

When you indicate to use async methods, does streamz support this? When I try, it indicates that my download_file method was never awaited. Or maybe you were indicating to use async methods and asyncio.wait outside of streamz?

Anyway, I guess Dask can do what I want as you mentioned but I need some sets of tasks (e.g. download + process) to be executed on the same dask worker since it can be a different machine (different fs).

I didn't catch the last commit date, but streamz still looks useful! Thanks

[martindurant]

When you indicate to use async methods, does streamz support this?

Yes, there should be some examples of this.

Dask can do what I want as you mentioned but I need some sets of tasks (e.g. download + process) to be executed on the same dask worker

There are various ways to do this kind of thing, but having shared storage is a useful thing for a cluster. I'm not immediately sure how you would phrase "download X can happen anywhere, but processing must happen where its associated download happened".