➜

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 gregory.p.smith
Recipients christian.heimes, gregory.p.smith, pitrou
Date 2008-03-23.01:24:17
SpamBayes Score 0.04645273
Marked as misclassified No
Message-id <1206235461.21.0.316781650669.issue2013@psf.upfronthosting.co.za>
In-reply-to
Content 
Looking at how much memory was actually used by PyLongObjects the way
our code allocates them... we can use this freelist for 2 digit PyLongs
on 32-bit systems and for 4 digit PyLongs on 64-bit systems.  Doing this
speeds things up even more as numbers > 32767 are still quite common.

why?  sizeof(PyVarObject) == 12, sizeof(digit) == 2.  Objects/obmalloc.c
allocates on 8, 16 and 32 byte boundaries.  Theres no such thing as a 14
byte allocation, its 16 byte aligned.  The same applies for 64-bit
platforms where the sizeof(PyVarObject) == 24, our allocation size is 32
 bytes there.

patch attached as -gps02.
History
Date User Action Args
2008-03-23 01:24:21gregory.p.smithsetspambayes_score: 0.0464527 -> 0.04645273
recipients: + gregory.p.smith, pitrou, christian.heimes
2008-03-23 01:24:21gregory.p.smithsetspambayes_score: 0.0464527 -> 0.0464527
messageid: <1206235461.21.0.316781650669.issue2013@psf.upfronthosting.co.za>
2008-03-23 01:24:20gregory.p.smithlinkissue2013 messages
2008-03-23 01:24:19gregory.p.smithcreate