On Fri, 10 Feb 2012 19:36:52 +0100 "M.-A. Lemburg" <mal@egenix.com> wrote:
In cases where the GIL does cause problems, it's usually better to consider changing the application design and use asynchronous processing with a single threaded design or a multi-process design where each of the processes only uses a low number of threads (20-50 per process).
Just a warning: mixing threads and forks can be hazardous to your sanity. In particular, forking a process that has threads running has behaviors, problems and solutions that vary between Unix variants. Best to make sure you've done all your forks before you create a thread if you want your code to be portable. <mike -- Mike Meyer <mwm@mired.org> http://www.mired.org/ Independent Software developer/SCM consultant, email for more information. O< ascii ribbon campaign - stop html mail - www.asciiribbon.org