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 mark.dickinson
Recipients christian.heimes, eric.smith, jkloth, mark.dickinson, python-dev, vstinner, zach.ware
Date 2013-11-26.20:02:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1385496153.36.0.0659861888213.issue19638@psf.upfronthosting.co.za>
In-reply-to
Content
Peak memory usage appears to be around 4 times the string length on Python 3.3, and around 3 times the string length on Python 3.4.

For 3.4, the peak occurs while formatting the exception message;  presumably at that point we've got all three of (a) the original string, (b) the exception message string being built, and (c) some sort of temporary string used during formatting.

For the purposes of this issue, I'll update the constants in the bigmemtest decorators.
History
Date User Action Args
2013-11-26 20:02:33mark.dickinsonsetrecipients: + mark.dickinson, vstinner, eric.smith, christian.heimes, jkloth, python-dev, zach.ware
2013-11-26 20:02:33mark.dickinsonsetmessageid: <1385496153.36.0.0659861888213.issue19638@psf.upfronthosting.co.za>
2013-11-26 20:02:33mark.dickinsonlinkissue19638 messages
2013-11-26 20:02:33mark.dickinsoncreate