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, skip.montanaro
Date 2015-05-28.17:42:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1432834920.8.0.163565862278.issue24318@psf.upfronthosting.co.za>
In-reply-to
Content
The Makefile's default "make all" target is meant for developers and iterative development.

make profile-opt is not.

If anything, this issue should document it somewhere if we even have docs on how to make "release" builds of something.  Realistically Debian already uses profile-opt for its binary builds.  I _believe_ the rpm based distros do as well (but I haven't checked, someone else can confirm).  Anyone else not doing so, please look at what debian does:

make profile-opt PROFILE_TASK="..."

where ... is regrtest.py given a test exclusion list of some of the longer running more annoying ones.

Not using a profile-opt builds in production is costing you ~10-40% in CPU performance.  This advice applies to all programs, not only python. :)
History
Date User Action Args
2015-05-28 17:42:00gregory.p.smithsetrecipients: + gregory.p.smith, skip.montanaro
2015-05-28 17:42:00gregory.p.smithsetmessageid: <1432834920.8.0.163565862278.issue24318@psf.upfronthosting.co.za>
2015-05-28 17:42:00gregory.p.smithlinkissue24318 messages
2015-05-28 17:42:00gregory.p.smithcreate