traverseda
/
cpython
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Issue #14200: Add benchmark results to text flow.

This commit is contained in:
Martin v. Löwis 2012-03-06 08:42:17 +01:00
parent 064474134c
commit de157cc5bc
1 changed files with 10 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
Doc/whatsnew/3.3.rst
View File

@ -167,19 +167,16 @@ The storage of Unicode strings now depends on the highest codepoint in the strin
* non-BMP strings (``U+10000-U+10FFFF``) use 4 bytes per codepoint. * non-BMP strings (``U+10000-U+10FFFF``) use 4 bytes per codepoint.
The net effect is that for most applications, memory usage of string storage The net effect is that for most applications, memory usage of string
should decrease significantly - especially compared to former wide unicode storage should decrease significantly - especially compared to former
builds - as, in many cases, strings will be pure ASCII even in international wide unicode builds - as, in many cases, strings will be pure ASCII
contexts (because many strings store non-human language data, such as XML even in international contexts (because many strings store non-human
fragments, HTTP headers, JSON-encoded data, etc.). We also hope that it language data, such as XML fragments, HTTP headers, JSON-encoded data,
will, for the same reasons, increase CPU cache efficiency on non-trivial etc.). We also hope that it will, for the same reasons, increase CPU
applications. cache efficiency on non-trivial applications. The memory usage of
Python 3.3 is two to three times smaller than Python 3.2, and a little
.. The memory usage of Python 3.3 is two to three times smaller than Python 3.2, bit better than Python 2.7, on a Django benchmark (see the PEP for
and a little bit better than Python 2.7, on a `Django benchmark details).
<http://mail.python.org/pipermail/python-dev/2011-September/113714.html>`_.
XXX The result should be moved in the PEP and a link to the PEP should
be added here.
PEP 3151: Reworking the OS and IO exception hierarchy PEP 3151: Reworking the OS and IO exception hierarchy