joepie91/pegjs
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity
pegjs/benchmark
History
David Majda b901a5c37a Rewrite benchmark/README.md 
More clarity, better grammar (hopefully).
2014-05-09 15:09:54 +02:00
..
css Added a benchmark suite. 2010-03-29 20:18:54 +02:00
json Added a benchmark suite. 2010-03-29 20:18:54 +02:00
vendor Add license to all vendored libraries where it was missing 2013-12-15 21:42:50 +01:00
benchmarks.js Factor out parts of benchmarks unrelated to running in the browser 2011-01-26 12:59:29 +01:00
index.css Code generator rewrite 2013-01-01 16:38:09 +01:00
index.html Update version to 0.8.0 2013-12-24 08:24:35 +01:00
index.js Code generator rewrite 2013-01-01 16:38:09 +01:00
README.md Rewrite benchmark/README.md 2014-05-09 15:09:54 +02:00
run benchmark/run: Always parse the -n/--run-count value as decimal integer 2013-12-15 21:45:54 +01:00
runner.js Make benchmark suite support |trackLineAndColumn| option 2012-03-26 20:16:19 +02:00

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 and Python installed.

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

    $ npm install

  3. Build browser version of PEG.js:

    $ make browser

  4. Serve PEG.js root directory using a web server:

    $ python -m SimpleHTTPServer

  5. Point your browser to the benchmark suite.

  6. Click the Run button and wait for results.