Author vstinner
Recipients DazWorrall, Dima.Tisnek, Michele, Omer.Katz, aconrad, alex, andrix, arigo, brian.curtin, carljm, coderanger, cool-RR, corona10, dabeaz, donaldjeo, durin42, eric.araujo, eric.smith, flox, gregory.p.smith, hozn, jab, jcea, jhylton, jmehnle, karld, kevinwatters, konryd, larry, loewis, mahmoudimus, movement, ncoghlan, neologix, nirai, phsilva, pitrou, portante, rcohen, rh0dium, scoder, tarek, thouis, victorpoluceno, vstinner, ysj.ray
Date 2020-10-08.11:24:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1602156262.7.0.958269547923.issue7946@roundup.psfhosted.org>
In-reply-to
Content
If someone wants to close this issue, I suggest to write a short section in the Python documentation to give some highlights on the available options and stategies to maximize performances and list drawbacks of each method. Examples:

* Multiple threads (threading): limited by the GIL
* Multiple processes (concurrent.futures, multiprocessing, distributed application): limited by shared data
* Concurrent programming (asyncio): limited to 1 thread

These architectures are not exclusive. asyncio can use multiple threads and be distributed in multiple processes.

I would be bad to go too deep into the technical details, but I think that we can describe some advantages and drawbacks which are common on all platforms.
History
Date User Action Args
2020-10-08 11:24:22vstinnersetrecipients: + vstinner, loewis, jhylton, arigo, gregory.p.smith, jcea, ncoghlan, pitrou, scoder, movement, larry, eric.smith, kevinwatters, tarek, karld, carljm, coderanger, phsilva, durin42, eric.araujo, nirai, alex, andrix, konryd, jab, brian.curtin, hozn, victorpoluceno, flox, DazWorrall, cool-RR, rh0dium, rcohen, dabeaz, mahmoudimus, portante, aconrad, ysj.ray, neologix, thouis, donaldjeo, Michele, jmehnle, Dima.Tisnek, Omer.Katz, corona10
2020-10-08 11:24:22vstinnersetmessageid: <1602156262.7.0.958269547923.issue7946@roundup.psfhosted.org>
2020-10-08 11:24:22vstinnerlinkissue7946 messages
2020-10-08 11:24:22vstinnercreate