News for hackers. Stuff that matters.
Re:Let's Remove the Global Interpreter Lock by ant6n on Monday August 14, 2017 @11:13AM (#15009181)
It gets more interesting when you have a large data set that's required for the computation, but as you compute, you may discover partial solutions that can be cached and used by other workers.

So not only a large read-only data set, but also a read-write cache used by all workers. This sort of thing is relatively easy with threads, but basically impossible with multiprocessing.

Re:Let's Remove the Global Interpreter Lock by dom0 on Monday August 14, 2017 @12:07PM (#15009708)
Depending on where you want to go and the application, such things may be good idea for a low number of workers but can become a major bottleneck.