[Python-Dev] Benchmarks: Comparison between Python 2.7 and Python 3.6 performance
Guido van Rossum
guido at python.org
Mon Nov 7 14:20:57 EST 2016
That's suspiciously close to the core sprint. Since the -S time stayed
roughly the same I suspect that either a new module was added to the
startup sequence or one of the (too many) modules already involved grew a
lot. My money is on a new module. Using `python -v -c pass` on a Python
built from the Sept. 9 tree and one built from Sept. 15, it shouldn't be
too hard to figure out which new module(s).
On Mon, Nov 7, 2016 at 7:11 AM, Wolfgang Maier <
wolfgang.maier at biologie.uni-freiburg.de> wrote:
> On 05.11.2016 10:56, Antoine Pitrou wrote:
>> Hi Victor,
>> On Fri, 4 Nov 2016 13:53:10 +0100
>> Victor Stinner <victor.stinner at gmail.com> wrote:
>>> Raw results of Python 3.6 compared to Python 2.7:
>> That's interesting, but I would be personally more interested in
>> a performance comparison of 3.5 and 3.6, to know if anything
>> interesting (or worrying :-)) has happened there.
> You can get this as well from https://speed.python.org/comparison/
> and https://speed.python.org/timeline and looking at this, I think there
> is something worrying indeed:
> Startup time has increased by ~ 30 % between 3.5 and 3.6 again. More
> specifically, all this increase happened between Sep 09 and Sep 15.
> I have no clue why that is, but it is definitely the biggest effect far
> and wide.
> The performance differences between 2.7 and 3.x are quite well-known by
>> now, and none of them are really dramatic except for the increase in
>> startup time.
> Python-Dev mailing list
> Python-Dev at python.org
> Unsubscribe: https://mail.python.org/mailman/options/python-dev/guido%
--Guido van Rossum (python.org/~guido)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Python-Dev