[MLton-devel] nucleic benchmark times

Matthew Fluet fluet@CS.Cornell.EDU
Wed, 13 Nov 2002 20:21:38 -0500 (EST)


> > Comparing -detect-overflow {true,false} yields more anomalies.
> ...
> > DLXSim is again an unexplained outlier, and I think it skews the MLton2 <=
> > MLton0 average quite a bit.  Looking through the benchmarks above, the
> > violations (other than DLXSim) are all < 0.07 (which is still a little odd
> > that there are any violations).
>
> Yeah.  The only worrying one is DLXSim.

I couldn't recreate the DLXSim -detect-overflow {false,true} anomaly on my
local machine with profiling, so I reran just DLXSim and got:

run time ratio
benchmark    MLton1 MLton2 MLton3 MLton4 MLton5 MLton6
DLXSimulator   1.07   0.99   1.05   1.08   1.07   1.07

which is much more reasonable.



-------------------------------------------------------
This sf.net email is sponsored by: Are you worried about 
your web server security? Click here for a FREE Thawte 
Apache SSL Guide and answer your Apache SSL security 
needs: http://www.gothawte.com/rd523.html
_______________________________________________
MLton-devel mailing list
MLton-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mlton-devel