This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pitrou
Recipients ajaksu2, amaury.forgeotdarc, collinwinter, eric.smith, ezio.melotti, gvanrossum, jafo, jimjjewett, lemburg, orivej, pitrou, rhettinger
Date 2009-06-04.11:26:11
SpamBayes Score 0.000327973
Marked as misclassified No
Message-id <1244114906.4913.1.camel@localhost>
In-reply-to <4A27A7EE.4010309@egenix.com>
Content
> Since pymalloc is being used to manage such objects, there's
> a lot of room for improvements, since the allocation scheme
> is under out control. E.g. we could have pymalloc allocate
> larger pools for PyUnicodeObjects.

I'm not sure what "larger pools for PyUnicodeObjects" means. pymalloc
doesn't have separate pools per object type, only per object size.
OTOH, we could grow the size limit under which pymalloc is used,
especially on 64-bit systems.
History
Date User Action Args
2009-06-04 11:26:17pitrousetrecipients: + pitrou, lemburg, gvanrossum, collinwinter, rhettinger, jafo, jimjjewett, amaury.forgeotdarc, eric.smith, ajaksu2, orivej, ezio.melotti
2009-06-04 11:26:13pitroulinkissue1943 messages
2009-06-04 11:26:12pitroucreate