Skip to content

Dart 2: Dart Analysis Server consume too many resources #33925

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
sestegra opened this issue Jul 20, 2018 · 2 comments
Closed

Dart 2: Dart Analysis Server consume too many resources #33925

sestegra opened this issue Jul 20, 2018 · 2 comments
Labels
devexp-server Issues related to some aspect of the analysis server legacy-area-analyzer Use area-devexp instead.

Comments

@sestegra
Copy link
Contributor

Dart VM version: 2.0.0-dev.68.0 (Tue Jul 10 14:47:26 2018 +0200) on "macos_x64"

I've just migrated from Dart 1.24.3 to Dart 2.0.0-dev.68.0.
Before the migration, I was running Webstorm with debug like a charm, CPU and RAM consumption were good.

Now, my CPU is continuously burning and RAM consumption is extremely high 3 times about 2G.

  • dartanalyzer.dart.snapshot
  • analysis_server.dart.snapshot
  • webdev serve

Why the performance changed so dramatically ?

@vsmenon vsmenon added legacy-area-analyzer Use area-devexp instead. devexp-server Issues related to some aspect of the analysis server labels Jul 23, 2018
@sestegra
Copy link
Contributor Author

During the migration, Dart Analyzer got around 3000 errors (due to strong mode issues that I had to fix) and around 1000 warnings (false positive coming from Angular plugin).

After fixing the errors and deactivating the Angular plugin, I noticed better performance, but lower than Dart 1. I guess it's related to #33257

@bwilkerson
Copy link
Member

I'm assuming this is stale. If you're still seeing this kind of performance, please let us know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
devexp-server Issues related to some aspect of the analysis server legacy-area-analyzer Use area-devexp instead.
Projects
None yet
Development

No branches or pull requests

3 participants