From: Rene Rivera (grafikrobot_at_[hidden])
Date: 2006-09-05 01:03:13
K. Noel Belcourt wrote:
> left bjam with a 1.7Gb memory footprint, leaving very little memory
> for the build phase on this 2Gb machine.
Yea, it's a painful effect of the string handling of bjam :-( There
aren't that many options for fixing it short of a rewrite to C++ which
someone, wish I could remember his name now, is working on.
> Is there anyway I can get bjam to release some memory once the
> dependency analysis is complete and it moves into the build phase?
Hm, it might be possible... But it would require identifying and
segregating the strings that the build phase needs into a separate
table so we could then delete the rest of the strings. Not sure how hard
that would be though.
> With our applications, there are a significant number of dependencies
> and I understand it takes lots of memory to do the dependency
> analysis but I'd like to find a way to free up some memory for the
> compiles and links.
You might want to do a couple of runs with "-d+10 -n -a" to get a
performance table dump. It would give us an idea of where it's spending
most of the time and memory. You can post the dump to the list.
I guess another approach would be to rewrite only some part of bjam in
C++. Not sure what would be most beneficial though.
-- -- 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