Re: https://speed.python.org/timeline/#/?exe=4&ben=python_startup&env=1&revs=50&equid=off&quarts=on&extr=on

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@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@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.

Regards

Antoine.



_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: https://mail.python.org/mailman/options/python-dev/guido%40python.org



--
--Guido van Rossum (python.org/~guido)