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 tim.peters
Recipients facundobatista, gtang, tim.peters
Date 2008-06-08.17:29:32
SpamBayes Score 0.002829531
Marked as misclassified No
Message-id <1212946174.84.0.0065556947211.issue3063@psf.upfronthosting.co.za>
In-reply-to
Content
Float objects also require, as do all Python objects, space to hold a
type pointer and a reference count.  So each float object requires at
least 16 bytes (on most 32-bit boxes, 4 bytes for the type pointer, 4
bytes for the refcount, + 8 bytes for the float).  So 100 million float
objects requires at least 1.6 billion bytes.

It is a gc issue in the sense that the float-object free-list is both
unbounded and immortal.  For that matter, so is the int-object
free-list.  This has been discussed many times over the years on
python-dev, but nobody yet has a thoroughly attractive alternative.
History
Date User Action Args
2008-06-08 17:29:40tim.peterssetspambayes_score: 0.00282953 -> 0.002829531
recipients: + tim.peters, facundobatista, gtang
2008-06-08 17:29:35tim.peterssetspambayes_score: 0.00282953 -> 0.00282953
messageid: <1212946174.84.0.0065556947211.issue3063@psf.upfronthosting.co.za>
2008-06-08 17:29:34tim.peterslinkissue3063 messages
2008-06-08 17:29:32tim.peterscreate