diff --git a/collects/tests/mzscheme/benchmarks/common/README.txt b/collects/tests/mzscheme/benchmarks/common/README.txt index cc79243730..ab3f7585a4 100644 --- a/collects/tests/mzscheme/benchmarks/common/README.txt +++ b/collects/tests/mzscheme/benchmarks/common/README.txt @@ -1,7 +1,7 @@ To run a benchmark, assuming you have `mzscheme' in your path: ./auto.ss ... where names an implementation as one of - mzscheme3m + mzscheme bigloo chicken gambit @@ -17,8 +17,8 @@ or any of the above prefixed by "no-" to skip the corresponding and benchmarks, run ./auto.ss --show -Naming no implementation/benchmark causes a standard of them to be run -(as reported by --show). Similarly, if the first named +Naming no implementation/benchmark causes a standard set of them to be +run (as reported by --show). Similarly, if the first named implementation/benchmak starts with "no-", the default set is used minus the "no-"-specified implementation/benchmark. @@ -36,7 +36,7 @@ All benchmarks must be run from the directory containing this file. Most bechmarks were obtained from http://www.cs.cmu.edu/afs/cs/project/ai-repository/ai/lang/scheme/code/bench/gabriel/ http://www.ccs.neu.edu/home/will/GC/sourcecode.html - Marc Feeley (who has all of them and more) + Marc Feeley Files that end in ".sch" are supposed to be standard Scheme plus `time'. Files that end in ".ss" are MzScheme wrapper modules or helper scripts. @@ -47,4 +47,4 @@ To build .sch directly with Gambit, Bigloo, or Chicken: mzscheme -qr mk-chicken.ss ; Unpack "dynamic-input.txt.gz" if you want to run the "dynamic" benchmark, -but the auto.ss script will do that for you. +but the "auto.ss" script will do that for you. diff --git a/collects/tests/mzscheme/benchmarks/common/index-template.html b/collects/tests/mzscheme/benchmarks/common/index-template.html index 03d1126c69..7f49f71c0c 100644 --- a/collects/tests/mzscheme/benchmarks/common/index-template.html +++ b/collects/tests/mzscheme/benchmarks/common/index-template.html @@ -1,14 +1,12 @@ -Some Scheme Benchmarks: Compilers +Some Scheme Benchmarks

About the Benchmarks

-

The benchmark page shows some +

The benchmark results page shows some benchmark results on a collection of fairly standard (mostly - Gabriel) Scheme benchmarks. (See also the - extended compilers and - interepreters results.)

+ Gabriel) Scheme benchmarks.

Tables show relative performance, with the actual time for the fastest run shown on the left. So, by @@ -18,14 +16,18 @@ benchmark didn't run in an implementation for some reason (possibly not a good one).

-

Small gray numbers are (relative) -compile times, where the compile time for the nothing -benchmark is subtracted from every other benchmark's compile -time.

+

+The compilers-only page shows +just the compilers among the tested implementations. For those +results, the small gray numbers are (relative) compile times, where +the compile time for the nothing benchmark is subtracted from +every other benchmark's compile time.

-

Run times are averaged over three runs. All reported times are CPU time (system plus user). - The times are based on the output of the implementation's time - syntactic form or similar functions.

+

Run times are averaged over three runs for compilers or one run for + interpreters. All reported times are CPU time (system plus user). + The times are based on the output of the + implementation's time syntactic form or similar + functions.

Machine:

    @@ -38,16 +40,19 @@ time.

  • Chicken (4.3.0): -no-trace -no-lambda-info -optimize-level 3 -block -lambda-lift
  • Gambit (4.6.0): (declare (block) (standard-bindings) (extended-bindings) (safe) (interrupts-enabled)), compiled and run with -:m10000
    • +
  • Guile (1.8.7): load
  • Ikarus (0.0.4-rc1+ rev 1870): in R6RS library
  • Larceny (0.97): in R6RS library
  • MIT (7.7.90+): (declare (usual-integrations)); run with --heap 12000
    • +
  • Petite Chez (7.4d): load
  • PLT (4.2.4): in module; for benchmarks that use set-car! and set-cdr!, PLT's R5RS support is used
    • +
  • Scheme48 (1.8): load after ,bench on
-These configurations are all “safe mode,” but they allow the compiler -to assume that built-in Scheme functions are not redefined and that no top-level defintion is ever -changed. Such assumptions correspond to putting the benchmark in an -R6RS library.

+These configurations are all “safe mode,” but they allow a +compiler to assume that built-in Scheme functions are not redefined +and that no top-level defintion is ever changed. Such assumptions +correspond to putting the benchmark in an R6RS library.

In general, we attempt to use the various implementations in a compentent way, but not in a sophisticated way. For example, we do not tweak @@ -56,7 +61,7 @@ R6RS library.

For more benchmarks and a more sophisticated use of a few compilers, including fixnum- and flonum-specific arithmetic as well as unsafe modes, - see this other page.

+ see Gambit benchmark results.

For further details on the benchmarks here, see the benchmark source and infrastructure, which is available form the PLT SVN repository: