On Sat, Aug 4, 2012 at 2:36 PM, David Cournapeau courn...@gmail.com wrote:
On Sat, Aug 4, 2012 at 12:14 PM, Aron Ahmadia a...@ahmadia.net wrote:
Hi David,
Apple's response here is somewhat confusing, but I will add that on the
supercomputing side of things we rarely fork, as this is not
Hi,
During last PyCon, Olivier Grisel (from scikits-learn fame) and myself
looked into a nasty bug on mac os x: https://gist.github.com/2027412.
The short story is that I believe this means numpy cannot be used with
multiprocessing if linked against accelerate framework, and as such we
should
Hi David,
Apple's response here is somewhat confusing, but I will add that on the
supercomputing side of things we rarely fork, as this is not well-supported
from the vendors or the hardware (it's hard enough to performantly spawn
500,000 processes statically, doing this dynamically becomes even
On 08/04/2012 01:14 PM, Aron Ahmadia wrote:
Hi David,
Apple's response here is somewhat confusing, but I will add that on the
supercomputing side of things we rarely fork, as this is not
well-supported from the vendors or the hardware (it's hard enough to
performantly spawn 500,000 processes
On Sat, Aug 4, 2012 at 12:14 PM, Aron Ahmadia a...@ahmadia.net wrote:
Hi David,
Apple's response here is somewhat confusing, but I will add that on the
supercomputing side of things we rarely fork, as this is not well-supported
from the vendors or the hardware (it's hard enough to
Responding to both Dag and David,
OpenMP is pretty widespread in supercomputing, and so is OpenMP +
multiple threads using LAPACK at the same time. This does NOT sound like
any issue with multiprocessing to me.
These are built on dynamic thread-level (pthreads), not process-level
