I wouldn't bother profiling within DrRacket. I think that feature might
still be for small student programs.
For doing performance tuning, you can do *some* of it within DrRacket
(like comparing the timings of many iterations of two different
implementations of a function), but then you have
Don't run profiling within drracket. DrRacket is a wonderful IDE
(and I use it on a daily basis for almost all my Racket programming)
but profiling in drracjet is broken and unreliable in information
gathering. (Keep in mind that DrRacket is an OS running atop of an
OS (linux, windows, mac), whic
Greetings, racketeers.
I have recently completed a port of most a large scripting language program I
wrote (large by my standards, which is on the order of tens of thousands of
lines of code) into pure Racket from some other scripting language, with the
object of getting faster execution.
Now
3 matches
Mail list logo
