History

David Majda 9648ca53d7 Use the "eslint-disable" directive instead of "eslint" The "eslint-disable" directive is more specific.		2016-09-22 17:05:42 +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	Use jQuery.scrollTo 2.1.2	2016-08-02 16:36:29 +02:00
.eslintrc.json	Pass benchmark code through Babel before serving it to the browser	2016-09-08 14:53:12 +02:00
benchmarks.js	Avoid aligning object keys	2016-09-22 07:55:30 +02:00
index.css	Code generator rewrite	2013-01-01 16:38:09 +01:00
index.html	Pass benchmark code through Babel before serving it to the browser	2016-09-08 14:53:12 +02:00
index.js	Sort "require" calls by variable names and group them	2016-09-22 16:59:47 +02:00
README.md	Pass benchmark code through Babel before serving it to the browser	2016-09-08 14:53:12 +02:00
run	Use the "eslint-disable" directive instead of "eslint"	2016-09-22 17:05:42 +02:00
runner.js	Move "use strict" directives up	2016-09-22 16:43:42 +02:00
server	Use the "eslint-disable" directive instead of "eslint"	2016-09-22 17:05:42 +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).

Install all PEG.js dependencies, including development ones:
```
$ npm install
```
Execute the benchmark suite:
```
$ make spec
```
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).

Make sure you have Node.js installed.
Install all PEG.js dependencies, including development ones:
```
$ npm install
```
Serve the benchmark suite using a web server:
```
$ benchmark/server
```
Point your browser to the benchmark suite.
Click the Run button and wait for results.