Re:An introduction to parallel programming using Python's mu...
by freyrs3 on Saturday July 12, 2014 @07:01PM
(#8026045)
If you're working on CPU-bound tasks with NumPy/SciPy using threads then you have to think very hard to make sure most of the critical sections are hitting the NumPy calls in C which release the GIL. It's not a great reliable way to program. The way the author describes is basically the only pure-Python way of achieving parallelism for this kind of problem.
[ Parent
| on HN ]
Re:An introduction to parallel programming using Python's mu...
by zobzu on Saturday July 12, 2014 @07:10PM
(#8026072)
it doesnt make it any less true. besides, that C python's GIL sucks doesnt mean threading or event models sucks.
In doubt, ask nginx how they feel about that. Then ask apache's mpn-prefork how that feels.
Re:An introduction to parallel programming using Python's mu...
by freyrs3 on Saturday July 12, 2014 @07:14PM
(#8026076)
If you're holding a global mutex every 100 instructions while context switching between CPU bound tasks, then yes, the GIL does suck. There are a class of IO-bound problems where threading/evented models in Python can be used effectively but that's not the class of problems the author is talking about here.