History

Paul Gschwendtner 4d88b4bc26 ci: do not run benchmark measurements in circleci (#34753 )

Currently we run all benchmark perf tests in CircleCI. Since we do not
collect any results, we unnecessarily waste CI/RBE resources. Instead,
we should just not run benchmark perf tests in CI, but still run the
functionality e2e tests which ensure that benchmarks are not broken.

We can do this by splitting the perf and e2e tests into separate
files/targets.

PR Close #34753

2020-01-29 09:22:27 -08:00

e2e_test/old

build: convert largeform benchmarks to bazel (#28645 )

2019-02-13 12:15:01 -08:00

src

ci: do not run benchmark measurements in circleci (#34753 )

2020-01-29 09:22:27 -08:00

benchmark_test.bzl

ci: do not run benchmark measurements in circleci (#34753 )

2020-01-29 09:22:27 -08:00

BUILD.bazel

build: update instructions to run benchmark tests (#28645 )

2019-02-13 12:15:01 -08:00

e2e_test.bzl

ci: do not run benchmark measurements in circleci (#34753 )

2020-01-29 09:22:27 -08:00

README.md

build: update instructions to run benchmark tests (#28645 )

2019-02-13 12:15:01 -08:00

start-server.js

build: update to nodejs rules 0.34.0 and bazel 0.28.1 (#31824 )

2019-07-26 15:01:25 -07:00

tsconfig-build.json

build: serve benchmark tree examples with bazel (#28568 )

2019-02-08 13:37:36 -08:00

tsconfig-e2e.json

build: convert largeform benchmarks to bazel (#28645 )

2019-02-13 12:15:01 -08:00

README.md

How to run the benchmarks locally

Run in the browser

yarn bazel run modules/benchmarks/src/tree/{name}:devserver

# e.g. "ng2" tree benchmark:
yarn bazel run modules/benchmarks/src/tree/ng2:devserver

Run e2e tests

# Run e2e tests of individual applications:
yarn bazel test modules/benchmarks/src/tree/ng2/...

# Run all e2e tests:
yarn bazel test modules/benchmarks/...

Use of *_aot.ts files

The *_aot.ts files are used as entry-points within Google to run the benchmark tests. These are still built as part of the corresponding ng_module rule.