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 georg.brandl
Recipients Ramchandra Apte, deleted250130, georg.brandl
Date 2013-01-09.13:09:44
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1357736984.4.0.151055843678.issue16908@psf.upfronthosting.co.za>
In-reply-to
Content
The "performance" you're measuring here is mostly startup, i.e. loading all necessary modules.  On Python 3, there is more to load, e.g. the filesystem encoding, therefore startup takes a little longer.

There are efforts to improve startup time, see e.g. #16101.

The memory consumption is expected, again due to more modules loaded.  You cannot make any statement about the memory usage of a real-world application by just measuring the overhead of the interpreter.

The memory usage due to strings should be very similar to Python 2 starting with Python 3.3, due to PEP 393.
History
Date User Action Args
2013-01-09 13:09:44georg.brandlsetrecipients: + georg.brandl, deleted250130, Ramchandra Apte
2013-01-09 13:09:44georg.brandlsetmessageid: <1357736984.4.0.151055843678.issue16908@psf.upfronthosting.co.za>
2013-01-09 13:09:44georg.brandllinkissue16908 messages
2013-01-09 13:09:44georg.brandlcreate
Morty Proxy This is a proxified and sanitized view of the page, visit original site.