[Python-Dev] GIL, Python 3, and MP vs. UP
Florian Weimer
fw at deneb.enyo.de
Mon Sep 19 23:17:13 CEST 2005
More information about the Python-Dev mailing list
Mon Sep 19 23:17:13 CEST 2005
- Previous message: [Python-Dev] GIL, Python 3, and MP vs. UP
- Next message: [Python-Dev] GIL, Python 3, and MP vs. UP
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
* Michael Hudson: > Not to my knowledge. I've always thought that it would be pretty > hard. I'd be interested in being proved wrong. The real problem is that you can ditch most extension modules. 8-( It sounds more like a fun project for the Python core, though. >> Copying GC might help to get rid of the GIL *and* improve performance >> in the accept+fork model (because read-only object access does not >> trigger copy-on-write anymore). > > How does a copying gc differ much from a non-copying non-refcounted gc > here? You could copy immutable objects to a separate set of pages and never collect them (especially if recursively refer to immutable objects only).
- Previous message: [Python-Dev] GIL, Python 3, and MP vs. UP
- Next message: [Python-Dev] GIL, Python 3, and MP vs. UP
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list