performance

Jan 9, 2016

57f8054 · Jan 9, 2016

This branch is 136 commits behind Netflix/falcor:master.

Name	Name	Last commit message	Last commit date
parent directory ..
formatter	formatter	Cleaned up and refactored some reporting stuff again	Jul 8, 2015
models	models	Fixed to reflect new falcor index location	Jul 17, 2015
reporters	reporters	Cleaned up and refactored some reporting stuff again	Jul 8, 2015
scripts	scripts	Added script to transform perf CSV results to averages for CI plots	Jul 28, 2015
tests	tests	feat(performance): The last of the statically referred to keys.	Jan 9, 2016
README.md	README.md	Added a readme for perf tests	Jul 27, 2015
TriggerDataSource.js	TriggerDataSource.js	found a bug with the performance tests that caused a memory leak.	Aug 31, 2015
browser.js	browser.js	updated the tests to become more modular.	Aug 25, 2015
device.js	device.js	updated the tests to become more modular.	Aug 25, 2015
karma.conf.js	karma.conf.js	Added explicit current minor versions	Sep 1, 2015
node.js	node.js	updated the tests to become more modular.	Aug 25, 2015
testRunner.js	testRunner.js	some updates of the program to handle performance testing.	Aug 25, 2015

README.md

gulp run perf

 Runs performance tests on configured browsers, and NodeJS, after building bundles.

gulp perf-all

 Build bundles for browser/device testing.

Browser tests are run through Karma, which should be installed locally as an npm devDependency.

All results will be saved to CSV files in the performance/out directory.

To run tests on other browsers:

karma start --browsers=[comma separated list of browsers]

For example:

karma start --browsers=Firefox, Chrome

It's worth noting that running performance tests in parallel on multiple browsers may impact results.

performance/browser.js

 Defines the tests and configuration to use for browser performance tests.

performance/node.js

 Defines the tests and configuration to use for NodeJS performance tests.