Hi Semi:
The real question is: how to NOT use multithreading, eh? :)
Seriously though, if anyone has figured out a solid way to integrate Matlab
multithreading, I'd love to hear about it as well! It seems to automatically
assume it has access to all cores on a box, so the only integration paths that
I can see would involve reserving whole nodes.
For us, if users want to use multiple cores they need to use matlabpool. We
'force' singlethreading for Matlab and all workers by modifying the matlab and
worker scripts in $MATLAB_ROOT/bin (we're running 2012a but should work for
2011b and probably others) as follows:
# diff matlab.dist matlab
483c483
< arglist=""
---
> arglist="-singleCompThread"
# diff worker.dist worker
20c20
< exec "${bindir}/matlab" -dmlworker -nodisplay -r distcomp_evaluate_filetask $*
---
> exec "${bindir}/matlab" -singleCompThread -dmlworker -nodisplay -r
> distcomp_evaluate_filetask $*
Obviously we also would prefer to be able to integrate the multithreading
correctly with SGE. It would make the "SGE Experience" nicer for our users ...
code that works on their quad-core desktop would then "just work" with more
cores on our bigger SGE nodes, and startup times would be faster as well.
Cheers, Hugh
-----Original Message-----
From: [email protected] [mailto:[email protected]] On
Behalf Of Semi
Sent: Wednesday, September 12, 2012 7:49 AM
To: [email protected]
Subject: [gridengine users] How possible to use matlab in mutithreading mode on
SGE?
_______________________________________________
users mailing list
[email protected]
https://gridengine.org/mailman/listinfo/users
_______________________________________________
users mailing list
[email protected]
https://gridengine.org/mailman/listinfo/users