➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Omer.Katz
Recipients DazWorrall, Dima.Tisnek, Michele, Omer.Katz, aconrad, alex, andrix, brian.curtin, carljm, coderanger, cool-RR, dabeaz, djc, donaldjeo, durin42, eric.araujo, eric.smith, flox, gregory.p.smith, hozn, 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 2019-06-24.13:31:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1561383063.96.0.364930390669.issue7946@roundup.psfhosted.org>
In-reply-to
Content 
Celery 5 is going async and in order to isolate the main event loop from task execution, the tasks are going to be executed in a different thread with it's own event loop.

This thread may or may not be CPU bound.
The main thread is I/O bound.

This patch should help a lot.

I like Nir's approach a lot (although I haven't looked into the patch itself yet). It's pretty novel.
David's patch is also very interesting.

I'm willing to help.
History
Date User Action Args
2019-06-24 13:31:04Omer.Katzsetrecipients: + Omer.Katz, loewis, jhylton, gregory.p.smith, jcea, ncoghlan, pitrou, scoder, vstinner, movement, larry, eric.smith, kevinwatters, tarek, djc, karld, carljm, coderanger, phsilva, durin42, eric.araujo, nirai, alex, andrix, konryd, brian.curtin, hozn, victorpoluceno, flox, DazWorrall, cool-RR, rh0dium, rcohen, dabeaz, mahmoudimus, portante, aconrad, ysj.ray, neologix, thouis, donaldjeo, Michele, jmehnle, Dima.Tisnek
2019-06-24 13:31:03Omer.Katzsetmessageid: <1561383063.96.0.364930390669.issue7946@roundup.psfhosted.org>
2019-06-24 13:31:03Omer.Katzlinkissue7946 messages
2019-06-24 13:31:03Omer.Katzcreate