Chance Ginger wrote: > Not quite that simple. In most modern OS's today there is something > called COW - copy on write. What happens is when you fork a process > it will make an identical copy. Whenever the forked process does > write will it make a copy of the memory. So it isn't quite as bad.
A noteable exception is a toy OS from a manufacturer in Redmond, Washington. It does not do COW fork. It does not even fork. To make a server system scale well on Windows you need to use threads, not processes. That is why the global interpreter lock sucks so badly on Windows. -- http://mail.python.org/mailman/listinfo/python-list