From: David Abrahams (dave_at_[hidden])
Date: 2003-03-19 06:47:42
Vladimir Prus <ghost_at_[hidden]> writes:
>> <A> SLOW, SLOW, SLOW! Worse than GNU Make in some cases. If this
>> can't be solved, BJam/Boost.Build is a dead end for me.
> I hope they can be solved. Please note that only about one performance
> optimization was done until now. When JÍrgen Hunold reported 60 mins delay,
> some actions were evidently needed (and I believe the delay is down to 2 mins
> now). Interesting, that the code which caused that slowdown was never
> considered performance critical.
> This means that performance optimization is yet to be done, and as we discover
> performance problems (with the help of big projects like yours), we'll fix
> them. Attempting to predict how much performance we'll get is impossible.But
> I think considerable improvement is possible. After all, we can add as many
> Jam builins as we'd need, and C is fast.
Are we sure this one wasn't due to header scanning? AFAIK we haven't
turned on the header dependency cache yet. That's so trivial to do
that it seems like low-hanging fruit.
In fact, Ali can check this himself. Just set HCACHEFILE in your
environment or on the bjam command-line to something like "./.jamdeps"
The first build thereafter should be slow but the rest should go faster.
-- Dave Abrahams Boost Consulting www.boost-consulting.com
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk