TSV Utilities release with LTO and PGO enabled
Johan Engelen
j at j.nl
Tue Jan 16 22:04:52 UTC 2018
On Tuesday, 16 January 2018 at 02:45:39 UTC, Jon Degenhardt wrote:
> On Tuesday, 16 January 2018 at 00:19:24 UTC, Martin Nowak wrote:
>> On Sunday, 14 January 2018 at 23:18:42 UTC, Jon Degenhardt
>> wrote:
>>> Combined, LTO and PGO resulted in performance improvements
>>> greater than 25% on three of my standard six benchmarks, and
>>> five of the six improved at least 8%.
>>
>> Yay, I'm usually seeing double digit improvements for PGO
>> alone, and single digit improvements for LTO. Meaning PGO has
>> more effect even though LTO seems to be the more hyped one.
>> Have you bothered benchmarking them separately?
>
> Last spring I made a few quick tests of both separately. That
> was just against the app code, without druntime/phobos. Saw
> some benefit from LTO, mainly one of the tools, and not much
> from PGO.
Because PGO optimizes for the given profile, it would help a lot
if you clarified how you do your PGO benchmarking. What kind of
test load profile you used for optimization and what test load
you use for the time measurement.
Regardless, it's fun to hear your test results :-)
Johan
More information about the Digitalmars-d-announce
mailing list