[webkit-dev] Compile time increase over time

JF Bastien jfb at chromium.org
Mon Apr 24 11:15:24 PDT 2017

On Mon, Apr 24, 2017 at 11:10 AM, Alex Christensen <achristensen at apple.com>

> Thanks for the data, Carlos! This is a growing problem that is hurting
> productivity.  We’ve discussed it a bit and haven’t done enough about it.
> Here are some of the ideas I’ve heard:
> 1) Reduce #includes by doing more forward declaring and less inlining.  We
> would probably need link time optimization to not lose performance benefits
> of inlining functions in headers.


> 2) Use distributed build tools and caches to cover up the problem.  WebKit
> would still be prohibitively hard to compile for people without lots of
> expensive computers, but we could greatly improve the productivity of large
> teams.
> 3) Use C++ modules


> 4) Put more commonly included headers into precompiled headers
> 5) I remember somebody claiming a few years ago that replacing #include
> “Something.h” with #include “path/to/Something.h” reduced compile times
> because it required fewer include paths, but I don’t think anybody has
> measured the improvement recently.
> 6) Optimize the compilers we use
> We should look into all of these and more.  Compiling WebKit also uses a
> lot of memory, and our binary size continues to increase.
> _______________________________________________
> webkit-dev mailing list
> webkit-dev at lists.webkit.org
> https://lists.webkit.org/mailman/listinfo/webkit-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-dev/attachments/20170424/21b8ae88/attachment.html>

More information about the webkit-dev mailing list