| commit | 20248e1c2e804cebe039624f32a413a8ee923a38 | [log] [tgz] |
|---|---|---|
| author | Martin Kustermann <kustermann@google.com> | Tue May 30 13:54:57 2023 +0000 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue May 30 13:54:57 2023 +0000 |
| tree | 37e44e646a27db11ad3557c7ce41fadd74ebc0c5 | |
| parent | 76f803a41caf6f4c37c0514b5954a77fb869046c [diff] |
[vm] Make vm/dart/isolates/reload_many_isolates_live_and_die_test more robust This test is launcing a subprocess with N parallel tracks. Each track is effectively a child isolate that will make a tail call to another child isolate. This process will continue until a reload is requested. => So it tests performing hot-reload of an application that has a lot of isolate creation, initialization, destructions in it. Right now it uses N=20 for normal architectures (and N=2 for simulators). It turns out that part of the slowness of this test is due to the subprocess's "vm-service" sending massive amounts of data via the websocket to the parent process that performs reloading: Each isolate will produce 4 events: * IsolateStart * IsolateRunnable * ServiceExtensionAdded * IsolateExit and send those to the `vm-service` isolate. The service isolate will then send those further via the WebSocket API to the parent process. => For 400k isolates this may send 3 GB of data via websocket. => The individual events most likely result in individual syscalls. => Networking stack on windows/mac may not be soo good, which would explain why it's more likely to time out there vs linux We ensure the helper reload utilites unsubscribe to the "isolate" stream once there's no longer a need for it. => This will avoid the 3 GB of network traffic. => It will avoid a subset (but not all) of the isolate -> vm-service events Issue https://github.com/dart-lang/sdk/issues/51347 TEST=vm/dart{,_2}/isolates/reload_many_isolates_live_and_die_test Change-Id: I971b983a08ea8febd38e8b40a53ed6b114c4daca Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/306421 Reviewed-by: Slava Egorov <vegorov@google.com> Commit-Queue: Martin Kustermann <kustermann@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.