[racket-dev] Surprising timings for loading Typed Racket

On Thu, Jul 12, 2012 at 3:20 PM, Matthew Flatt <mflatt at cs.utah.edu> wrote:
> Of course, we usually optimize for long-term performance, and it's
> sometimes tricky to balance short-term and long-term performance. Does
> the difference that you see still matter when a program does something
> useful?

If I run the Shootout typed mandelbrot set benchmark in the tree, like
this (after adding #lang :

% time r -l racket/base -t tmandel.rkt 1000 > /dev/null
real	0m0.495s
user	0m0.460s
sys	0m0.032s

% time r -t tmandel.rkt 1000 > /dev/null
real	0m0.551s
user	0m0.516s
sys	0m0.032s

Still a pretty short computation, but the overhead there.
-- 
sam th
samth at ccs.neu.edu