RetroSearch Browse

Fri Mar 3 07:10:11 EST 2017 · https://mail.python.org/pipermail/python-dev/2017-March/147532.html

And that is the reason I wanted to test this a bit more.

However it adds a maintenance burden when fast fixes need to be applied (aka now that Fedora 26 alpha is being prepared). The build now due to the arm architecture and the huge test suite takes approximately 3 hours and 30 minutes. Increasing that by two hours is not something I would do during the development phase.

On another note, RHEL's python does not have the PGO functionality backported to it.

Regards,

Charalampos Stratakis
Associate Software Engineer
Python Maintenance Team, Red Hat

----- Original Message -----
From: "Victor Stinner" <victor.stinner at gmail.com>
To: "Charalampos Stratakis" <cstratak at redhat.com>
Cc: "Nick Coghlan" <ncoghlan at gmail.com>, "Barry Warsaw" <barry at python.org>, "Python-Dev" <python-dev at python.org>
Sent: Friday, March 3, 2017 12:53:00 PM
Subject: Re: [Python-Dev] Help requested with Python 2.7 performance regression

2017-03-03 12:18 GMT+01:00 Charalampos Stratakis <cstratak at redhat.com>:
> PGO is not enabled in RHEL and Fedora.
>
> I did some initial testing for Fedora, however it increased the compilation time of the RPM by approximately two hours, so for the time being I left it out.

Two hours in a *single* build server is very cheap compared to the
10-20% speedup on *all* computers using this PGO build, no?

Victor

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2017-March/147532.html below:

[Python-Dev] Help requested with Python 2.7 performance regression