react/scripts/bench
Jack Hou e8e62ebb59 use different eslint config for es6 and es5 (#11794)
* use different eslint config for es6 and es5

* remove confusing eslint/baseConfig.js & add more eslint setting for es5, es6

* more clear way to run eslint on es5 & es6 file

* seperate ESNext, ES6, ES6 path, and use different lint config

* rename eslint config file & update eslint rules

* Undo yarn.lock changes

* Rename a file

* Remove unnecessary exceptions

* Refactor a little bit

* Refactor and tweak the logic

* Minor issues
2017-12-11 15:52:46 +00:00
..
benchmarks use different eslint config for es6 and es5 (#11794) 2017-12-11 15:52:46 +00:00
benchmark.js Run prettier on scripts/bench (#9671) 2017-05-11 16:14:17 -07:00
build.js Fix benchmark runner (#11749) 2017-12-02 00:00:29 +00:00
package.json Pin lighthouse at 2.0.0 2017-12-04 13:23:30 +00:00
README.md Fix benchmark runner (#11749) 2017-12-02 00:00:29 +00:00
runner.js Fix benchmark runner (#11749) 2017-12-02 00:00:29 +00:00
server.js Fix a few typos (#10860) 2017-09-27 11:13:21 +01:00
stats.js Fix benchmark runner (#11749) 2017-12-02 00:00:29 +00:00
yarn.lock Pin lighthouse at 2.0.0 2017-12-04 13:23:30 +00:00

React Benchmarking

Commands

In most cases, the only two commands you might want to use are:

  • yarn start
  • yarn build core,dom-client --type=UMD_PROD && yarn start --skip-build

The first command will run benchmarks with all the default settings. A local and remote build will occur on React and ReactDOM UMD bundles, both local and remote repos will be run against all benchmarks.

The second command will run all benchmarks but skip the build process. This is useful for when doing local performance tweaking and the remote repo has already had its bundles built. Both local and remote repos will be run against all benchmarks with this command too.

The other commands are as follows:

# will compare local repo vs remote merge base repo
yarn start

# will compare local repo vs remote merge base repo
# this can significantly improve bench times due to no build
yarn start --skip-build

# will only build and run local repo against benchmarks (no remote values will be shown)
yarn start --local

# will only build and run remote merge base repo against benchmarks (no local values will be shown)
yarn start --remote

# will only build and run remote master repo against benchmarks
yarn start --remote=master

# same as "yarn start"
yarn start --remote --local

# runs benchmarks with Chrome in headless mode
yarn start --headless

# runs only specific string matching benchmarks
yarn start --benchmark=hacker