Analyzer cold performance (performance) #33039
Labels
analyzer-stability
area-dart-model
For issues related to conformance to the language spec in the parser, compilers or the CLI analyzer.
model-performance
Performance/memory issues in analyzer/cfe
P2
A bug or feature request we're likely to work on
type-enhancement
A request for a change that isn't a bug
type-performance
Issue relates to performance or code size
Comments
bwilkerson
added
legacy-area-analyzer
Hixie
changed the title
johnniwinther
added
area-dart-model
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When you first start working on a project, the analyzer takes a long time to get started. This manifests as slow bots, long wait times when teaching someone something new, and generally results in a poor first impression of analyzer performance.
A representative benchmark for this is the
analyzer_benchmark flutter_repo_watchnumber on Flutter's performance dashboard. Currently, it takes over 70s to do a cold analysis of Flutter.To reproduce this, delete the analyzer cache, check out the Flutter framework, then run
flutter analyze --flutter-repo --watch --benchmark.The text was updated successfully, but these errors were encountered: