From: David Abrahams (dave_at_[hidden])
Date: 2006-09-05 14:55:33
Alex Besogonov <cyberax_at_[hidden]> writes:
> Rene Rivera 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.
> That's me :) My C++ port is Almost Ready (tm)
> There's another possible solution, we can use Boehm-Demers-Weiser
> conservative GC (http://www.hpl.hp.com/personal/Hans_Boehm/gc/). I
> tried to use it with BJam some time ago with good results but forgot
> to write about it here.
What are you collecting with the GC? List nodes? How much can that
I think we want to be collecting strings. We could do it by
allocating the string cache hashtable in untraced memory and
registering a finalizer for each string that removes its entry from
-- 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