The data contained in this repository can be downloaded to your computer using one of several clients.
Please see the documentation of your version control software client for more information.

Please select the desired protocol below to get the URL.

This URL has Read-Only access.

Statistics
| Branch: | Revision:

main_repo / deps / v8 / benchmarks / README.txt @ 40c0f755

History | View | Annotate | Download (1.81 KB)

1
V8 Benchmark Suite
2
==================
3

    
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
6
individual benchmarks are included in the JavaScript files.
7

    
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
10
benchmark files, and two benchmark runners: An HTML version (run.html)
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.
30

    
31

    
32
Changes From Version 2 To Version 3
33
===================================
34

    
35
Version 3 adds a new benchmark, RegExp.  The RegExp benchmark is
36
generated by loading 50 of the most popular pages on the web and
37
logging all regexp operations performed.  Each operation is given a
38
weight that is calculated from an estimate of the popularity of the
39
pages where it occurs and the number of times it is executed while
40
loading each page.  Finally the literal letters in the data are
41
encoded using ROT13 in a way that does not affect how the regexps
42
match their input.