Thanks for all the suggestions, the 'keywords' gave me some good pointers. I am unable to try them out as I'm at work but think I know where to go tonight.
I found reference to: sys.setcheckinterval(interval) Which can change the number of python 'instructions' executed between thread swaps (default value is 100). However I don't think that this will help as the thread is locked up in C/C++ code. I also found this document which looks more promising: http://teckla.idyll.org/~t/transfer/public/day3.pdf It explains how the thread model/GIL prevents wrapper code running on multiple cores, but does suggest this handy hint: -- Basically, just wrap I/O blocking code or CPU-intensive code in the following macros: Py_BEGIN_ALLOW_THREADS ...Do some time-consuming operation... Py_END_ALLOW_THREADS -- I have access to change the wrapper code, so I'll give that a go first, Simon. PS. appologies for the double post, finger trouble with web-mail client. _______________________________________________ clug-talk mailing list [email protected] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
