Daniel DeLorme wrote:

> The problem goes further than that. Even if you were to load your libs 
> in one process and then fork off worker processes (using copy-on-write 
> to share loaded code), the gargabe collector writes to *every* page in 
> memory when doing a garbage collecting run, thus negating the benefits 
> of COW. It's fixed in 1.9, thankfully, but 1.8 is going to be a memory 
> hog no matter which way you look at it.

What does 1.9 do differently?

-- 
       vjoel : Joel VanderWerf : path berkeley edu : 510 665 3407