angular-docs-cn

History

crisbeto 664e0015d4 perf(ivy): replace select instruction with advance (#32516 )

Replaces the `select` instruction with a new one called `advance`. Instead of the jumping to a specific index, the new instruction goes forward X amount of elements. The advantage of doing this is that it should generate code the compresses better.

PR Close #32516

2019-09-10 06:30:28 -04:00

element_text_create

perf(ivy): introduce a node-based micro-benchmarks harness (#32510 )

2019-09-09 15:56:41 -04:00

interpolation

perf(ivy): replace select instruction with advance (#32516 )

2019-09-10 06:30:28 -04:00

map_based_style_and_class_bindings

perf(ivy): replace select instruction with advance (#32516 )

2019-09-10 06:30:28 -04:00

noop_change_detection

test(ivy): add style binding node-based micro benchmark (#32104 )

2019-08-15 09:55:03 -07:00

property_binding

perf(ivy): replace select instruction with advance (#32516 )

2019-09-10 06:30:28 -04:00

style_and_class_bindings

perf(ivy): replace select instruction with advance (#32516 )

2019-09-10 06:30:28 -04:00

style_binding

perf(ivy): replace select instruction with advance (#32516 )

2019-09-10 06:30:28 -04:00

BUILD.bazel

perf(ivy): introduce a node-based micro-benchmarks harness (#32510 )

2019-09-09 15:56:41 -04:00

micro_bench.ts

perf(ivy): introduce a node-based micro-benchmarks harness (#32510 )

2019-09-09 15:56:41 -04:00

noop_renderer.ts

perf(ivy): add a micro benchmark for style and class bindings (#32401 )

2019-08-30 13:52:35 -04:00

README.md

perf(ivy): introduce a node-based micro-benchmarks harness (#32510 )

2019-09-09 15:56:41 -04:00

setup.ts

perf(ivy): add element and text creation benchmark (#32342 )

2019-08-28 17:12:38 -07:00

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