You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
David Majda c134e06229 Move "use strict" directives up
Move "use strict" directives to the first line of each file. In
particular, move them above any ESLint comments, which are far less
important.

There are few exceptions:

  Executable files

    In these, the "use strict" directive must give way to the shebang.

  lib/parser.js

    Here, the "Generated by..." comment comes first. Also, ESLint
    comments are prepended in post-processing.
8 years ago
..
css Added a benchmark suite. 14 years ago
json Added a benchmark suite. 14 years ago
vendor Use jQuery.scrollTo 2.1.2 8 years ago
.eslintrc.json Pass benchmark code through Babel before serving it to the browser 8 years ago
README.md Pass benchmark code through Babel before serving it to the browser 8 years ago
benchmarks.js Avoid aligning object keys 8 years ago
index.css Code generator rewrite 11 years ago
index.html Pass benchmark code through Babel before serving it to the browser 8 years ago
index.js Move "use strict" directives up 8 years ago
run Move "use strict" directives up 8 years ago
runner.js Move "use strict" directives up 8 years ago
server Move "use strict" directives up 8 years ago

README.md

PEG.js Benchmark Suite

This is the PEG.js benchmark suite. It measures speed of the parsers generated by PEG.js on various inputs. Its main goal is to provide data for code generator optimizations.

Running in Node.js

All commands in the following steps need to be executed in PEG.js root directory (one level up from this one).

  1. Install all PEG.js dependencies, including development ones:

    $ npm install
    
  2. Execute the benchmark suite:

    $ make spec
    
  3. Wait for results.

Running in the Browser

All commands in the following steps need to be executed in PEG.js root directory (one level up from this one).

  1. Make sure you have Node.js installed.

  2. Install all PEG.js dependencies, including development ones:

    $ npm install
    
  3. Serve the benchmark suite using a web server:

    $ benchmark/server
    
  4. Point your browser to the benchmark suite.

  5. Click the Run button and wait for results.