➜

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 methane
Recipients alecsandru.patrascu, brett.cannon, gregory.p.smith, lemburg, methane, pitrou, r.david.murray, scoder, skrah, steve.dower, zach.ware
Date 2016-03-05.00:22:05
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1457137325.61.0.875833896554.issue25702@psf.upfronthosting.co.za>
In-reply-to
Content 
> For sure you are not the only user that has active workloads on the physical machine while you do benchmarks :)

I think largest machine type I chosen (32core) can avoid sharing physical machine with other users.

> On the other hand, the path you are going with just LTO is nice for experiments, but for real-world usages is not feasible. Using it in conjunction with PGO is the way to have the best Python interpreter, and I strongly recommend for you to use the v04 versions of the patches.

I agree PGO+LTE is the best.  But I want "only LTO" because:

1) It is a pitfall that `./configure --with-lto && make` doesn't use LTO.
2) PGO makes build too slow.  For casual usecase, I can wait LTO but not PGO.
History
Date User Action Args
2016-03-05 00:22:05methanesetrecipients: + methane, lemburg, brett.cannon, gregory.p.smith, pitrou, scoder, r.david.murray, skrah, zach.ware, steve.dower, alecsandru.patrascu
2016-03-05 00:22:05methanesetmessageid: <1457137325.61.0.875833896554.issue25702@psf.upfronthosting.co.za>
2016-03-05 00:22:05methanelinkissue25702 messages
2016-03-05 00:22:05methanecreate