Programming

Performance in DrRacket

steloflute 2012. 9. 5. 23:30

http://docs.racket-lang.org/guide/performance.html

 

 

18.1 Performance in DrRacket

By default, DrRacket instruments programs for debugging, and debugging instrumentation can significantly degrade performance for some programs. Even when debugging is disabled through the Choose Language... dialog’s Show Details panel, the Preserve stacktrace checkbox is clicked by default, which also affects performance. Disabling debugging and stacktrace preservation provides performance results that are more consistent with running in plain racket.

Even so, DrRacket and programs developed within DrRacket use the same Racket virtual machine, so garbage collection times (see Memory Management) may be longer in DrRacket than when a program is run by itself, and DrRacket threads may impede execution of program threads. For the most reliable timing results for a program, run in plain racket instead of in the DrRacket development environment. Non-interactive mode should be used instead of the REPL to benefit from the module system. See Modules and Performance for details.

 

In short,

 

- Select "No debugging or profiling"

- Uncheck "Preserve stacktrace (disable some optimizations)"

 

'Programming' 카테고리의 다른 글

Try Clojure  (0) 2012.09.06
Best In Class: Python vs Clojure - Evolving  (0) 2012.09.06
Inferior Emacs Lisp Mode (ielm)  (0) 2012.09.05
(Go) Structs and Interfaces  (0) 2012.09.04
Schematics Scheme Cookbook  (0) 2012.09.04