From: Rene Rivera (grafikrobot_at_[hidden])
Date: 2007-10-25 02:01:47
Motonari Ito wrote:
> The biggest problem I have in bjam is its speed.
> We have 1M lines of code managed by Boost Build system (V2). Bjam takes
> 20-30 second (when current directory is root) or 5-6 second (when
> current directory is leaf) before starting actual compilations. It's
> very slow for daily compile & edit development.
Not bad... Boost testers that run many toolsets see a few times that.
And in my own project I see 2 minute startup times.
> So, I have profiled on the latest bjam (Milestone 12) with Rational
You can get more detailed information just by running:
bjam -d+10 -n -a ...
> It looks like memory and hash related functions are bottle
> neck - is there any chance to accelerate them?
There's always a chance ;-) And interesting ideas are welcome. Just make
sure to search the archives of this list to familiarize yourself with
the many attempts at improving the performance.
-- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo
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