| commit | d18893c7996dcee308905854da167682f170ccbd | [log] [tgz] |
|---|---|---|
| author | Jens Johansen <jensj@google.com> | Mon Apr 24 09:49:12 2023 +0000 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Apr 24 09:49:12 2023 +0000 |
| tree | 4f7c7a80f3c604a9fbf56d004f1fc215bf7f18de | |
| parent | fe01a2068db8e0e9f0c651e40cf549ff5a3e434e [diff] |
[CFE] Add more benchmarking points; change how subdivides are handled This CL adds more benchmarking points, specifically giving more insight into where body_buildBodies time goes. It furthermore changes how overlapping subdivides are handled. Previously only the first subdivide was actually recorded, meaning that if a subdivide `a` contained a subdivide `b` only subdivide `a` would have any time recorded for it. Now instead subdivide `b` will get data recorded for the time it runs; this time will then _not_ be added to `a`s total. For instance if subdivide `a` spends one second, then (while still being in subdivide `a`) we enter subdivide `b` and spend one second there, exit it, and spend yet another second before we exit subdivide `a` before we would just have recorded 3 seconds for subdivide `a`, now we will instead record 2 seconds for subdivide `a` and 1 second for subdivide `b`. Additionally a "system subdivide" is automatically added summarizing any unaccounted for subdivide time, and an extra entry describing the estimated subdivide recording overhead figues too. As an additional note, enabling benchmarking seems to add ~6-7% runtime, and because we specifically add additional parsing phases to measure that separately the token stream can change before doing the actual parsing, meaning that when enabling benchmarking some errors might be swallowed. Change-Id: I07ef42657c385031e8bb8680738442cf04fe2263 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/295540 Reviewed-by: Johnni Winther <johnniwinther@google.com> Commit-Queue: Jens Johansen <jensj@google.com>
Dart is:
Optimized for UI: Develop with a programming language specialized around the needs of user interface creation.
Productive: Make changes iteratively: use hot reload to see the result instantly in your running app.
Fast on all platforms: Compile to ARM & x64 machine code for mobile, desktop, and backend. Or compile to JavaScript for the web.
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 on our wiki.
The easiest way to contribute to Dart is to file issues.
You can also contribute patches, as described in Contributing.