Paul, On 14 December 2012 at 01:17, Paul Johnson wrote: | Dirk! | | Correct as usual!
[...] | Here's the evidence you are right. | | Before starting R, restrict openblas's use of threads in the environment | | $ export GOTO_NUM_THREADS=1 | | After that, HAPPY profiling in R! Right. If one has tried multithreading before as I have with (so-far unsuccessful) endeavours to get OpenMP into one particular package (while maintaining RNG outcomes / reproducibility) then those stack error look eerily familiar. All very frustrating because "it all just works" with one thread. And that is all R can handle, so if you multithread, set proper mutexes. And for profiling that very logic seems to require turning multithreading off. Cheers, Dirk -- Dirk Eddelbuettel | [email protected] | http://dirk.eddelbuettel.com _______________________________________________ R-SIG-Debian mailing list [email protected] https://stat.ethz.ch/mailman/listinfo/r-sig-debian
