[MLton-devel] first benchmarks with generational gc

[Stephen Weeks]

> Or, maybe it is exactly right.  The cost of (stop-and-copy) GC should be
> almost exactly the same with and without generational GC, because almost
> all of the reachable data will be in the nursery; i.e., we won't save much
> by stoping the trace at the old-generation boundary.  But, the nursery is
> half the size of the non-generational heap, so we're GCing twice as often.

Makes sense.

> Unfortunately, GC only seems to account for 22% of the benchmark, which
> doesn't seem enough to double the running time.

Hmm.  No idea here.  Feel free to play around with the latest checkin
if you want.


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
MLton-devel mailing list
MLton-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mlton-devel