Add note about modules vs REPL in performance docs.

This commit is contained in:
Vincent St-Amour 2011-05-24 10:41:44 -04:00
parent fcf766c905
commit c5973bea99

View File

@ -39,8 +39,10 @@ Racket virtual machine, so garbage collection times (see
@secref["gc-perf"]) may be longer in DrRacket than when a program is @secref["gc-perf"]) may be longer in DrRacket than when a program is
run by itself, and DrRacket threads may impede execution of program run by itself, and DrRacket threads may impede execution of program
threads. For the most reliable timing results for a program, run in threads. For the most reliable timing results for a program, run in
plain @exec{racket} instead of in the DrRacket development plain @exec{racket} instead of in the DrRacket development environment.
environment. Non-interactive mode should be used instead of the
@tech["REPL"] to benefit from the module system. See
@secref["modules-performance"] for details.
@; ---------------------------------------------------------------------- @; ----------------------------------------------------------------------
@ -82,7 +84,7 @@ difficult to detect.
@; ---------------------------------------------------------------------- @; ----------------------------------------------------------------------
@section{Modules and Performance} @section[#:tag "modules-performance"]{Modules and Performance}
The module system aids optimization by helping to ensure that The module system aids optimization by helping to ensure that
identifiers have the usual bindings. That is, the @racket[+] provided identifiers have the usual bindings. That is, the @racket[+] provided