| commit | 3873af28e9654857b4afdb5a074670589034746e | [log] [tgz] |
|---|---|---|
| author | Jens Johansen <jensj@google.com> | Tue Mar 11 00:22:15 2025 -0700 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Mar 11 00:22:15 2025 -0700 |
| tree | 3893085c90bad7afa376b2f10269919d0cdc43a9 | |
| parent | ad58bc01ca2533a17084e387cf3083498515f70c [diff] |
[analyzer server] Legacy protocol debounces getFixes and getAsssits requests too; benchmark In reports of the analyzer being slow we've seen `edit.getFixes` causing a long queue because they take longer to execute than the wait before the next one comes in. While we haven't been able to reproduce that, this CL adds a benchmark that fires *a lot* of both `edit.getFixes` (seen in reports from users) and `edit.getAssists` (which seems, locally at least, to happen every time the cursor moves), and debounces them, changing the benchmark results from ``` 4 files / CodeType.ImportCycle: Initial analysis: 1.322030 Completion after change: 3.096128 4 files / CodeType.ImportChain: Initial analysis: 1.361750 Completion after change: 3.500849 4 files / CodeType.ImportExportCycle: Initial analysis: 1.349346 Completion after change: 3.065497 4 files / CodeType.ImportExportChain: Initial analysis: 1.367151 Completion after change: 3.246891 4 files / CodeType.ImportCycleExportChain: Initial analysis: 1.360573 Completion after change: 3.393901 ``` to ``` 4 files / CodeType.ImportCycle: Initial analysis: 1.322070 Completion after change: 0.546532 4 files / CodeType.ImportChain: Initial analysis: 1.410870 Completion after change: 0.649789 4 files / CodeType.ImportExportCycle: Initial analysis: 1.349923 Completion after change: 0.741040 4 files / CodeType.ImportExportChain: Initial analysis: 1.360396 Completion after change: 0.638332 4 files / CodeType.ImportCycleExportChain: Initial analysis: 1.354682 Completion after change: 0.658086 ``` Change-Id: Icb0423133726e02e08e204b1c59209264889f8a6 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/413682 Commit-Queue: Jens Johansen <jensj@google.com> Reviewed-by: Phil Quitslund <pquitslund@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.