On Wednesday 27 October 2010 10:02:09 Tinne De Laet wrote:
> Hi,
>
> The BFL (sometimes) takes ages to compile.
> On my computer I usually stop the compilation after 15 minutes, then
> restart (and then it finishes in about 5 - 10 minutes)
> On our test farm we now have a case where the compilation took 8000s.
> Can we figure out why the compilation takes so long?

The only workaround we found was by having one type info creation per .cpp file
and not having multiple types in one .cpp file. Somehow, it's faster compiling
the separate files than to compile all-in-one.

Peter

Hey Tinne,

2010/10/27 Tinne De Laet <tinne [dot] delaet [..] ...>:
> Hi,
>
> The BFL (sometimes) takes ages to compile.
> On my computer I usually stop the compilation after 15 minutes, then
> restart (and then it finishes in about 5 - 10 minutes)
> On our test farm we now have a case where the compilation took 8000s.
> Can we figure out why the compilation takes so long?

Ruben noticed that it's probably the size of your RAM which determines
the speed. The cpp file is so big it consumes all RAM and then starts
using the swap. It's possible to speed up the compilation process by
splitting up the typekit.cpp file in a number of different files. I've
just send you a patch splitting up a bit already, which caused an
improvement of more then 50% already. It now took me 200secs on my pc
and 300s on a hudson farm - pc.

regards,

Steven

>
> The almost happy BFL maintainer,
>
> Tinne
> --
> Orocos-Users mailing list
> Orocos-Users [..] ...
> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>