| commit | 13d22de11556208d5a5690ca28a66950acaf7a1d | [log] [tgz] |
|---|---|---|
| author | Jens Johansen <jensj@google.com> | Thu May 30 11:25:35 2024 +0000 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu May 30 11:25:35 2024 +0000 |
| tree | a965834ef1635718d71966d52b7ef57a6add3793 | |
| parent | 6e5bb2cd5deba60c73b90f334c9b2e960f2816ca [diff] |
[CFE] Fix time-regression on using generateKernelInternal in expectation tests After 9a9b33eb0b950dec7524274e1eb06beb2e7ff020 running the strong suite (for instance) got noticeably slower. The most obvious change is the we no longer cache uri translators, and while that does add _something_, the main culprit for being quite a bit slower is that it now verifies all fuzzing compiles too. It didn't before. Before running 1 of 10 shards took ~43 seconds, spending ~0.7 seconds on getting uri translators and performing 298 verifications. Now running the same thing takes ~64 seconds (in round numbers that's +50%), spending ~3.7 seconds on getting uri translators and performing 3004 verifications. Disabling verification when fuzzing makes it go to taking ~51 seconds, spending ~4.2 seconds on getting uri translators and performing 298 verifications. The main reason for the getting more uri translators (for the same run, now: 1824, before: 293) is that the packages uri is now set on the options (i.e. is non-null) making the incremental compiler force getting a new uri translator (as the previous "known" was null, meaning that it "matched" before (both was null), but doesn't now). Fixing both of these and rerunning 5 times (turns out the runtimes vary quite a bit) I get to (in seconds): Before 9a9b33eb0b950dec7524274e1eb06beb2e7ff020: 43 50 49 43 45 With this CL: 44 50 46 52 47 Where there's "no difference proven at 95.0% confidence". Change-Id: Icc20083566cecb4daa27728c7801d50969d87e14 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/368643 Reviewed-by: Johnni Winther <johnniwinther@google.com> Commit-Queue: Jens Johansen <jensj@google.com>
Dart is:
Approachable: Develop with a strongly typed programming language that is consistent, concise, and offers modern language features like null safety and patterns.
Portable: Compile to ARM, x64, or RISC-V machine code for mobile, desktop, and backend. Compile to JavaScript or WebAssembly for the web.
Productive: Make changes iteratively: use hot reload to see the result instantly in your running app. Diagnose app issues using DevTools.
Dart's flexible compiler technology lets you run Dart code in different ways, depending on your target platform and goals:
Dart Native: For programs targeting devices (mobile, desktop, server, and more), Dart Native includes both a Dart VM with JIT (just-in-time) compilation and an AOT (ahead-of-time) compiler for producing machine code.
Dart Web: For programs targeting the web, Dart Web includes both a development time compiler (dartdevc) and a production time compiler (dart2js).
Dart is free and open source.
See LICENSE and PATENT_GRANT.
Visit dart.dev to learn more about the language, tools, and to find codelabs.
Browse pub.dev for more packages and libraries contributed by the community and the Dart team.
Our API reference documentation is published at api.dart.dev, based on the stable release. (We also publish docs from our beta and dev channels, as well as from the primary development branch).
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 in our repo at docs.
The easiest way to contribute to Dart is to file issues.
You can also contribute patches, as described in Contributing.
Future plans for Dart are included in the combined Dart and Flutter roadmap on the Flutter wiki.