[MLton-devel] Stop-and-copy / mark-compact switch criterion

[Alain Deutsch]

Fine with me. The only thing that I am not sure of is the
requirement you put in heapDesiredSize to have a live ratio of 1.5
in case we do not fit in RAM. Wouldn't it be safer to use the
older, more conservative constant 1.25 which may cause less paging
?

A related question: what is your estimate (or measurement) of the
relative cost of mark-compact vs. stop-and-copy (on the same heap
size) ?

--
Alain Deutsch, CTO              tel.: +33 (0)1 49 65 32 64
PolySpace Technologies          fax.: +33 (0)1 49 65 05 77
mailto:deutsch@POLYSPACE.COM    http://www.polyspace.com



-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?  Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
_______________________________________________
MLton-devel mailing list
MLton-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mlton-devel