OLD | NEW |
1 V8 Benchmark Suite | 1 V8 Benchmark Suite |
2 ================== | 2 ================== |
3 | 3 |
4 This is the V8 benchmark suite: A collection of pure JavaScript | 4 This is the V8 benchmark suite: A collection of pure JavaScript |
5 benchmarks that we have used to tune V8. The licenses for the | 5 benchmarks that we have used to tune V8. The licenses for the |
6 individual benchmarks are included in the JavaScript files. | 6 individual benchmarks are included in the JavaScript files. |
7 | 7 |
8 In addition to the benchmarks, the suite consists of the benchmark | 8 In addition to the benchmarks, the suite consists of the benchmark |
9 framework (base.js), which must be loaded before any of the individual | 9 framework (base.js), which must be loaded before any of the individual |
10 benchmark files, and two benchmark runners: An HTML version (run.html) | 10 benchmark files, and two benchmark runners: An HTML version (run.html) |
11 and a standalone JavaScript version (run.js). | 11 and a standalone JavaScript version (run.js). |
| 12 |
| 13 |
| 14 Changes From Version 1 To Version 2 |
| 15 =================================== |
| 16 |
| 17 For version 2 the crypto benchmark was fixed. Previously, the |
| 18 decryption stage was given plaintext as input, which resulted in an |
| 19 error. Now, the decryption stage is given the output of the |
| 20 encryption stage as input. The result is checked against the original |
| 21 plaintext. For this to give the correct results the crypto objects |
| 22 are reset for each iteration of the benchmark. In addition, the size |
| 23 of the plain text has been increased a little and the use of |
| 24 Math.random() and new Date() to build an RNG pool has been removed. |
| 25 |
| 26 Other benchmarks were fixed to do elementary verification of the |
| 27 results of their calculations. This is to avoid accidentally |
| 28 obtaining scores that are the result of an incorrect JavaScript engine |
| 29 optimization. |
OLD | NEW |