[webkit-dev] Building WebKit's GTK+ back-end using distcc timing

[Adrian Perez]

Hi Ilyes,

On Thu, 10 Mar 2011 13:51:48 +0100
Ilyes Gouta <ilyes.gouta at gmail.com> wrote:

> I don't think that the slowdown is due to the addition of new
> C++/code. Even building with most of the WebKit options turned off,
> actually takes that much of time.
> 
> By just observing how the files are dispatched to the distcc servers,
> how these are loaded by the client machine (which initiate the build),
> almost could tell that this latter is doing more work (slower, more
> preprocessor work?) for dispatching source code, than a
> pre-9161f3277b15aae8d15a929d5362e28cad7e01c0 commit code base. In our
> setup, the client machine which initiates the distributed build,
> doesn't contribute to it, i.e doesn't compile code, but just serves
> the source code.

As far as I know, distcc master process pre-processes the code before
sending it to the slaves. Having more (or bigger) files in the tree
could be the cause of your master machine having to do more work before
offloading the compilation to the slaves. Last, but not least, more code
means more work when linking libraries and programs, and this step is
also done by the distcc build master. There could me some other
additional reasons why it is taking so much time now, but I would point
to pre-processing and linking as possible causes for the distcc master
now doing more work.

Hope this helps, or provides some hint to help you troubleshoot your
builds.

Cheers,


-- 
Adrian Perez <aperez at igalia.com>
Igalia - Free Software Engineering
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.webkit.org/pipermail/webkit-dev/attachments/20110310/29fa8809/attachment.bin>