News for hackers. Stuff that matters.
Re:Celery, non-blocking code and quest against coroutines by TheGuyWhoCodes on Thursday June 09, 2016 @10:43AM (#11869680)
Celery is great and works well but it definitely doesn't fix the GIL problem.

Having shared memory is a must for some workloads, or can save you a ton of money, especially when taking about caching. Sometimes caching per process isn't feasible but caching for all threads is, even using multi processing isn't good enough because you can only use the main process memory if it's simple arrays.

Re:Celery, non-blocking code and quest against coroutines by mdomans on Thursday June 09, 2016 @11:11AM (#11869891)
Talking about shared memory benefits and overheads in Python is a pretty abstract problem, if you account for how much objects Python interpreter creates and what OS does under certain load levels.

I'm merely advocating a different model for concurrency in Python :)