v8/benchmarks
kasperl@chromium.org 8d617a7b6b Removed the use of Math.random() and new Date() for building
the RNG pool in the crypto benchmark.
Review URL: http://codereview.chromium.org/6071

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@404 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
2008-10-02 07:43:46 +00:00
..
base.js Removed the use of Math.random() and new Date() for building 2008-10-02 07:43:46 +00:00
crypto.js Removed the use of Math.random() and new Date() for building 2008-10-02 07:43:46 +00:00
deltablue.js Changed copyright header from google inc. to v8 project authors. 2008-09-09 20:08:45 +00:00
earley-boyer.js Introduce some checks to indicate that the benchmarks have run correctly. 2008-09-25 13:48:27 +00:00
raytrace.js Introduce some checks to indicate that the benchmarks have run correctly. 2008-09-25 13:48:27 +00:00
README.txt Removed the use of Math.random() and new Date() for building 2008-10-02 07:43:46 +00:00
richards.js Introduce some checks to indicate that the benchmarks have run correctly. 2008-09-25 13:48:27 +00:00
run.html Removed the use of Math.random() and new Date() for building 2008-10-02 07:43:46 +00:00
run.js Introduce some checks to indicate that the benchmarks have run correctly. 2008-09-25 13:48:27 +00:00
v8-logo.png Added version 1 of the V8 benchmark suite to the repository. 2008-09-02 11:06:49 +00:00

V8 Benchmark Suite
==================

This is the V8 benchmark suite: A collection of pure JavaScript
benchmarks that we have used to tune V8. The licenses for the
individual benchmarks are included in the JavaScript files.

In addition to the benchmarks, the suite consists of the benchmark
framework (base.js), which must be loaded before any of the individual
benchmark files, and two benchmark runners: An HTML version (run.html)
and a standalone JavaScript version (run.js).


Changes From Version 1 To Version 2
===================================

For version 2 the crypto benchmark was fixed.  Previously, the
decryption stage was given plaintext as input, which resulted in an
error.  Now, the decryption stage is given the output of the
encryption stage as input.  The result is checked against the original
plaintext.  For this to give the correct results the crypto objects
are reset for each iteration of the benchmark.  In addition, the size
of the plain text has been increased a little and the use of
Math.random() and new Date() to build an RNG pool has been removed.

Other benchmarks were fixed to do elementary verification of the
results of their calculations.  This is to avoid accidentally
obtaining scores that are the result of an incorrect JavaScript engine
optimization.