Home Original page

GIL in the new glossary

kosh kosh at aesaeion.com
Fri Oct 3 18:37:35 EDT 2003 
On Thursday 02 October 2003 15:37, дамјан г. wrote:

> Seriously, the biggest problem with GIL is in applications like mod_python,
> which is an Python extension to Apache. When Apache works in the
> multithreaded MPM (I think it was called "Worker") the GIL starts to be a
> serious bottleneck in your server performance. The GIL will lock your
> Apache threads if they happen to hit on a mod_python handled location.

Why use the multithreaded one? Why not just use the process one? When I have 
done some tests the multithreaded one was not any better then the multi 
process one on a linux box but I have not tested it on other operating 
systems. Also the multiprocess  one is more reliable in that it is more 
resistant to memory leaks, bugs that cause things to crash etc. In my mind 
multiple processes is how you scale to multiple cpus in the most reliable way 
currently. Zope does it that way also. You use zeo an then run one zope 
instance for each cpu you want it to use. It scales nicely.
More information about the Python-list mailing list