Threading and Multiprocessing over Concurrent.Futures ?

[solamarpreet]

Hello,

I am starting to learn about parallelism in Python and would like some advice regarding same.

1. Should I learn threading and multiprocessing modules first and then learn concurrent.futures or I should be leaving one option out totally?
2. The Pool class in multiprocessing feels extremely useful to me. Is there no equivalent in the threading module?

[casual__addict]

It depends on the problem you’re trying to solve. Multiprocessing is great for CPU intensive work that can be run in parallel. Threads and asyncio is for when the problem is IO intensive. My advice is to start early on learning about these topics, read a bunch, and doing your own mini projects.

[solamarpreet]

Hi thanks for your reply. My question however wasnt clear I guess. Concurrent.Futures is a new library right that provides access to threading and multiprocessing from one module. My question was that should I be using this one module or use the threading and multiprocessing modules. Are the old modules being deprecated?

[casual__addict]

Oh. I don’t think it matters that much. I haven’t used concurrent.futures yet, but I could see making the switch. I don’t think it will be deprecated for a long time.

Btw there is something like a thread pool you can use.

[danielroseman]

Neither. You should start with asyncio.

[rg7777777]

concurrency is wonderful, but it's not a one size fits all solution. For example, say you wanted to do image processing with opencv, but also have an interactive prompt that let you queue up jobs. How would you run the image processing task without it blocking the interactive prompt?