Re: status: separation of expansion/optimization/memoization/execution

[Han-Wen]

address@hidden writes:
> However, didn't you say that you had some nice benchmark application
> called lilypond ;-)  If there was a significant change due to your gc

:)

I ran some tests on the anomalous machine (50% gc time), now it's back
down to 15 to 20 % -- still a lot, but credible. Compared to the old
scheme there is some slight advantage (gc-times down from 70 to 25),
perhaps due to the new malloc trigger, but I also increased the
segment size (I fixed a silly bug in our use of putenv).


-- 
Han-Wen Nienhuys   |   address@hidden   |   http://www.cs.uu.nl/~hanwen