[MLton-user] Performances: mlton 20030716p1 V.S. 20051202

[Alexandre Langenieux]

>
> For 2 significant tests, we run between 15% and 30% slower than before.
>
> After quick analysis of binary parts that are slower, it seems (but 
> not yet sure
> that parts that need more memory are slower (Are we swapping ? we do
> not know yet, we need to track this).

After deeper analysis of our product memory management behavior, it appears
that for thoses 2 tests, we are now swapping a lot when compiling with 
mlton-2005
when we were not swapping at all with mlton-2003. This can explain our 
performances
regression.

So, does it exist compiling options for tuning memory management to 
return at
least to the same performances as with mlton-2003 ?