> As a historical note, when we first enabled PGO support for Windows our > profiling scenario was "start Firefox, wait 10 seconds, shut down > Firefox". Enabling PGO with this profiling run provided us with 20-25% > perf improvements in many of our benchmarks on Talos. We later changed > it to the current set of profiling data[1] (Blueprint CSS samples, the > SunSpider benchmark), and there was almost no visible change in the > Talos numbers.
This seems to indicate our current coverage isn't oriented toward performance gains users will see, and that there are potential gains to be found. All the more reason to keep pgo around a while longer and figure out how we can simplify testing with different test runs. > We should also remind that there would be an infra load win from > disabling Windows PGO builds. IMHO, if it's a choice between infra load and better performance in the end product, performance should win out. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
