On Wednesday, 17 January 2018 at 21:49:52 UTC, Johan Engelen
wrote:
On Wednesday, 17 January 2018 at 04:37:04 UTC, Jon Degenhardt
wrote:
Clearly personal judgment played a role. However, the tools
are reasonably task focused, and I did take basic steps to
ensure the benchmark data and tests
On Wednesday, 17 January 2018 at 04:37:04 UTC, Jon Degenhardt
wrote:
Clearly personal judgment played a role. However, the tools are
reasonably task focused, and I did take basic steps to ensure
the benchmark data and tests were separate from the training
data/tests. For these reasons, my
On Tuesday, 16 January 2018 at 22:04:52 UTC, Johan Engelen wrote:
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.
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
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%.
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
I just released a new version of eBay's TSV Utilities. The cool
thing about the release is not about changes in toolkit, but that
it was possible to build everything using LDC's support for Link
Time Optimization (LTO) and Profile Guided Optimization (PGO).
This includes running the
