On Wed, Mar 27, 2013 at 12:05 PM, Brent Fulgham <bfulg...@gmail.com> wrote:
> Hi Daniel, > > On Tue, Mar 26, 2013 at 11:21 AM, Daniel Bratell <brat...@opera.com>wrote: > >> As an experiment we took the (chromium) project webcore_dom, that >> normally compiles in 56 seconds in Windows on a generic computer and >> "fixed" it. Removing the many include paths in the build system and instead >> specifying the path in the include directives changed that to 42 seconds, a >> 25% reduction. >> > > I thought that much of this was supposed to be addressed by the use of > precompiled headers. Presumably, if the header files are properly > incorporated into the PCH, shouldn't any gains from relative paths be > small? Obviously your statistic says otherwise, but I'm not sure that a > single test on a single system is definitive proof of anything. > I thought PCHs are mostly for system headers that don't change often ( https://code.google.com/p/chromium/codesearch#chromium/src/third_party/WebKit/Source/WebCore/WebCorePrefix.h&q=WebCorePrefix&sq=package:chromium&type=cs), else every .h change would require recompiling _all_ cc files, no? > > Did you run the test multiple times to get a feel for how reproducible the > improvements was? I know I have fooled myself in the past into thinking I > had improved something, only to discover that unrelated computer activity > (e.g., backups, virus scans, etc.) were contributing to slow build times. > > -Brent > > > _______________________________________________ > webkit-dev mailing list > webkit-dev@lists.webkit.org > https://lists.webkit.org/mailman/listinfo/webkit-dev > >
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
