[Python-ideas] Copy-on-write when forking a python process

[Nick Coghlan]

On Fri, Apr 15, 2011 at 7:10 AM, Antoine Pitrou <solipsis at pitrou.net> wrote:
> On Wed, 13 Apr 2011 16:17:03 +1000
> Nick Coghlan <ncoghlan at gmail.com> wrote:
>> There's a clear workaround for the COW problem these days: use PyPy
>> instead of CPython :)
>
> Doesn't PyPy use a copying collector? Wouldn't that mean that the first
> garbage collector pass after the fork() would un-share the memory pages
> anyway?

I'm fairly sure one of the PyPy talks at Pycon specifically mentioned
the CoW problem as one of the ways PyPy was able to save memory over
CPython. The PyPy folks would be the ones to accurately answer
questions like that, though.

Cheers,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia