| commit | 2877d78576661d3cddd6546cb577f039ac8a1511 | [log] [tgz] |
|---|---|---|
| author | Derek Xu <derekx@google.com> | Fri Apr 25 08:51:22 2025 -0700 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Apr 25 08:51:22 2025 -0700 |
| tree | 3a6f40aeed8da2aa3733ac4c4e5d4f11a3b2d3fb | |
| parent | 9a3109518126a4a5427d18ead621d8d0d70deff2 [diff] |
Reland "[VM/Service] Record timeline events representing completed microtasks" This is a reland of commit 22021cc12014feffd33f9a3d50e37447a980b99b I showed some excerpts of Golem results to @mraleph for varying targets and constant CPU, patch A, and patch B. Those constants being: CPU: Intel Xeon patch A: revision=115869&patch=20143 patch B: revision=115876 (example results: https://golem.corp.goog/Comparison?repository=dart#targetA%3Ddart%3BmachineTypeA%3Dlinux-x64%3BrevisionA%3D115869%3BpatchA%3Dderekx-Reland---VM%2FService--Record-timeline-events-representing-completed-microtasks--4%3BtargetB%3Ddart%3BmachineTypeB%3Dlinux-x64%3BrevisionB%3D115876%3BpatchB%3DNone) He said that this change could be relanded as long as the following "RunTime as Score" regressions of the "dart" target were noted in the commit message: - StreamSingleSubTest: -3.907% (-0.8 noise) - ScheduleMicrotaskTest: -12.67% (-0.6 noise) TEST=pkg/vm_service/test/timeline_events_for_completed_microtasks_test Original change's description: > [VM/Service] Record timeline events representing completed microtasks > > TEST=pkg/vm_service/test/timeline_events_for_completed_microtasks_test > > CoreLibraryReviewExempt: This CL does not include any core library API > changes, it only modifies the implementation of microtasks (by > instrumenting them). > Change-Id: I54d886db9519c73f9e3218a9cc1c46bc9fe9acc3 > Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/420221 > Commit-Queue: Derek Xu <derekx@google.com> > Reviewed-by: Ben Konyi <bkonyi@google.com> CoreLibraryReviewExempt: This CL does not include any core library API changes, it only modifies the implementation of microtasks (by instrumenting them). Change-Id: Ia7741a9bb9ab948e8d5fff1cf9abe9915e247d81 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/423921 Reviewed-by: Ben Konyi <bkonyi@google.com> Commit-Queue: Derek Xu <derekx@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.