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 gregory.p.smith
Recipients gregory.p.smith, methane, nascheme, pablogsal, tianon
Date 2019-07-11.04:13:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1562818398.88.0.0779262478212.issue36044@roundup.psfhosted.org>
In-reply-to
Content
yeah I pulled a similar looking list of tests for the PROFILE_TASK to suggest to the Docker Python image maintainers - see https://github.com/docker-library/python/pull/404 and https://github.com/docker-library/python/issues/160.

I haven't run comparisons of that vs the default overly long profile task, but a comparison against a non PGO enabled cpython 3.7 build shows the types of speedups i'd expect from a decent PGO build.

doing proper comparisons against a full build would take a lot more time than I have right now.

It'd be reasonable to change the default task to something that is faster to build so long as we don't appear to be making major sacrifices in speed somewhere.

(your benchmark table's pickle result changes are inconsistent and odd, but that benchmark may not be very meaningful as written, i haven't looked at it)
History
Date User Action Args
2019-07-11 04:13:18gregory.p.smithsetrecipients: + gregory.p.smith, nascheme, methane, pablogsal, tianon
2019-07-11 04:13:18gregory.p.smithsetmessageid: <1562818398.88.0.0779262478212.issue36044@roundup.psfhosted.org>
2019-07-11 04:13:18gregory.p.smithlinkissue36044 messages
2019-07-11 04:13:18gregory.p.smithcreate