sjdevn...@yahoo.com wrote:
On Feb 18, 2:58 pm, John Nagle <na...@animats.com> wrote:
Multiple processes are not the answer. That means loading multiple
copies of the same code into different areas of memory. The cache
miss rate goes up accordingly.
A decent OS will use copy-on-write with forked processes, which should
carry through to the cache for the code.
That doesn't help much if you're using the subprocess module. The
C code of the interpreter is shared, but all the code generated from
Python is not.
This will get even worse when Unladen Swallow starts generating vast
swaths of unshared x86 instructions.
John Nagle
--
http://mail.python.org/mailman/listinfo/python-list
