Description
This is a collection of issues around the performance of the Dart VM Service. This becomes more salient when dealing with lower-end devices in particular.
Some of these bugs have been closed as either WAI or infeasible, but the issues end up resurfacing for Flutter developers when we try to tweak or just use tracing.
At a high level, we'd like to be in a world where we're confident that tracing and code coverage collection are as cheap as possible.
Category: Timeline
- OOM when using DevTools flutter/flutter#101002
- Consider using protozero rather than JSON for timeline recording #47631
- iOS: Dart_TimelineEvent is surprisingly slow #47850
Category: Coverage - although this has improved since @liamappelbe's work, it still uses an interchange format that's pretty bloated and expensive, which can hurt when trying to use it on device for things like integration tests.
- Tests with coverage takes 10x time than just running flutter test flutter/flutter#86722
- Improve coverage collection performance for large projects flutter/flutter#80516
/cc @gaaclarke @zanderso @jonahwilliams who may have more issues they're aware of to add to this.