joepie91
/
pegjs
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
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.
redux
master
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '057a93fbc7'
${ noResults }
pegjs/benchmark
History
David Majda e61c23c634 ESLint: Set environments better 
Instead of setting ESLint environment to "node" globally, set it on
per-directory basis using separate .eslintrc.json files:

  Directory   Environment
  -----------------------
  bin         node
  lib         commonjs
  spec        jasmine

It was impossible to use this approach for the "benchmark" directory
which contains a mix of files used in various environments. For
benchmark/run, the environment is set inline. For the other files, as
well as spec/helpers.js, the globals are declared manually (it is
impossible to express how these files are used just by a list of
environments).

Fixes #408.
 		9 years ago
..
css Added a benchmark suite. 15 years ago
json Added a benchmark suite. 15 years ago
vendor Update jQuery.scrollTo's LICENSE file 9 years ago
README.md Use sentence case consistently in {spec,benchmark}/README.md headers 11 years ago
benchmarks.js ESLint: Set environments better 9 years ago
index.css Code generator rewrite 12 years ago
index.html Update version to 0.9.0 9 years ago
index.js Fix ESLint errors in benchmark/index.js 9 years ago
run ESLint: Set environments better 9 years ago
runner.js ESLint: Set environments better 9 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 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.