mirror of
https://github.com/dart-lang/sdk
synced 2024-10-04 03:26:39 +00:00
e491bc5d86
This CL updates the frontend_server to allow specifying what dill file to initialize from. Normally, it tries to initialize from the same dill file as is the output. This is fine in many cases (e.g. flutter run always says it should output to build/app.dill): The first time it compiles everything, subsequent times (across restarts) it only recompiles what's needed. When running tests, however, the output is in a temporary directory, so it doesn't work across restarts. The startup time for tests is always rather high, because it always has to recompile everything. This CL updates the frontend_server to allow specifying what dill file to initialize from. Flutter can thus save the compiled test file in a centralized location (e.g. build/test.dill) and load from that across restarts. Plumbing this into flutter yields the following result, when running a single test (the one automatically created when creating a new flutter project): Before: ~5.5 seconds Now, first run: ~5.5 second (unchanged) Now, subsequent runs: ~3.4 seconds Approximate breakdown: Startup cost (e.g. if there's no test directory): ~ 800 ms Starting up the actual frontend server: ~150 ms Reading source from old dill, loading all relevant files and invalidating source: ~ 300 ms Compiling everything (or, rather, nothing as it's all from the dill at this point): ~ 650 ms Serializing: ~ 250 ms Copying files: ~ 50 ms Running the actual test: ~1100 ms Total: ~3300 ms `time flutter test --local-engine=host_debug --preview-dart-2` says ~3.4 seconds... To compare, --no-preview-dart-2 takes ~2.2 seconds, so dart2 still has a (significantly) higher startup cost. Moves the needle on https://github.com/flutter/flutter/issues/15767. Change-Id: I36a2d05bc76e0193d369df42eb3b9f08416dd78f Reviewed-on: https://dart-review.googlesource.com/51820 Reviewed-by: Kevin Millikin <kmillikin@google.com> Reviewed-by: Vyacheslav Egorov <vegorov@google.com> Commit-Queue: Jens Johansen <jensj@google.com> |
||
|---|---|---|
| .github | ||
| build | ||
| client | ||
| docs | ||
| pkg | ||
| runtime | ||
| samples | ||
| samples-dev | ||
| sdk | ||
| tests | ||
| third_party | ||
| tools | ||
| utils | ||
| .clang-format | ||
| .gitattributes | ||
| .gitignore | ||
| .gn | ||
| .mailmap | ||
| .packages | ||
| AUTHORS | ||
| BUILD.gn | ||
| CHANGELOG.md | ||
| codereview.settings | ||
| dartdoc_options.yaml | ||
| DEPS | ||
| LICENSE | ||
| PATENTS | ||
| PRESUBMIT.py | ||
| README.dart-sdk | ||
| README.md | ||
| WATCHLISTS | ||
Dart
Dart is an open-source, scalable programming language, with robust libraries and runtimes, for building web, server, and mobile apps.
Using Dart
Visit the dartlang.org to learn more about the language, tools, getting started, and more.
Browse pub.dartlang.org for more packages and libraries contributed by the community and the Dart team.
Building Dart
If you want to build Dart yourself, here is a guide to getting the source, preparing your machine to build the SDK, and building.
There are more documents on our wiki.
Contributing to Dart
The easiest way to contribute to Dart is to file issues.
You can also contribute patches, as described in Contributing.