angular-cn/packages/core/test/render3/perf/README.md

### Build

yarn bazel build //packages/core/test/render3/perf:{name}.min_debug.es2015.js --define=compile=aot

### Run 

node dist/bin/packages/core/test/render3/perf/{name}.min_debug.es2015.js

### Profile

node --no-turbo-inlining --inspect-brk dist/bin/packages/core/test/render3/perf/{name}.min_debug.es2015.js

then connect with a debugger (the `--inspect-brk` option will make sure that benchmark execution doesn't start until a debugger is connected and the code execution is manually resumed). 

The actual benchmark code has calls that will start (`console.profile`) and stop (`console.profileEnd`) a profiling session.

### Notes

In all the above commands {name} should be replaced with the actual benchmark (folder) name, ex.:
- build: `yarn bazel build //packages/core/test/render3/perf:noop_change_detection.min_debug.es2015.js --define=compile=aot`
- run: `time node dist/bin/packages/core/test/render3/perf/noop_change_detection.min_debug.es2015.js`
- profile: `node --no-turbo-inlining --inspect-brk dist/bin/packages/core/test/render3/perf/noop_change_detection.min_debug.es2015.js profile`
test(ivy): remove code duplication from node perf benchmarks (#32104) PR Close #32104 2019-08-12 06:31:15 -04:00			`### Build`

docs(ivy): update micro-benchmark instructions (#32190) PR Close #32190 2019-08-19 09:45:13 -04:00			`yarn bazel build //packages/core/test/render3/perf:{name}.min_debug.es2015.js --define=compile=aot`
test(ivy): remove code duplication from node perf benchmarks (#32104) PR Close #32104 2019-08-12 06:31:15 -04:00
			`### Run`

perf(ivy): introduce a node-based micro-benchmarks harness (#32510) PR Close #32510 2019-09-06 10:26:42 -04:00			`node dist/bin/packages/core/test/render3/perf/{name}.min_debug.es2015.js`
test(ivy): remove code duplication from node perf benchmarks (#32104) PR Close #32104 2019-08-12 06:31:15 -04:00
			`### Profile`

docs(ivy): update micro-benchmark instructions (#32190) PR Close #32190 2019-08-19 09:45:13 -04:00			`node --no-turbo-inlining --inspect-brk dist/bin/packages/core/test/render3/perf/{name}.min_debug.es2015.js`

			then connect with a debugger (the `--inspect-brk` option will make sure that benchmark execution doesn't start until a debugger is connected and the code execution is manually resumed).

			The actual benchmark code has calls that will start (`console.profile`) and stop (`console.profileEnd`) a profiling session.

			`### Notes`

			`In all the above commands {name} should be replaced with the actual benchmark (folder) name, ex.:`
			- build: `yarn bazel build //packages/core/test/render3/perf:noop_change_detection.min_debug.es2015.js --define=compile=aot`
			- run: `time node dist/bin/packages/core/test/render3/perf/noop_change_detection.min_debug.es2015.js`
perf(ivy): introduce a node-based micro-benchmarks harness (#32510) PR Close #32510 2019-09-06 10:26:42 -04:00			- profile: `node --no-turbo-inlining --inspect-brk dist/bin/packages/core/test/render3/perf/noop_change_detection.min_debug.es2015.js profile`