Skip to content
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

Startup time of extension is slower when using new analysis engine #1865

Closed
DonJayamanne opened this issue Jun 5, 2018 · 4 comments
Closed
Assignees
Labels
area-intellisense LSP-related functionality: auto-complete, docstrings, navigation, refactoring, etc. debt Covers everything internal: CI, testing, refactoring of the codebase, etc.
Milestone

Comments

@DonJayamanne
Copy link

  • With jedi loads in 700ms, with analysis loads in 1700ms
  • Need to improve caching of interpreter info
@DonJayamanne DonJayamanne added area-intellisense LSP-related functionality: auto-complete, docstrings, navigation, refactoring, etc. debt Covers everything internal: CI, testing, refactoring of the codebase, etc. labels Jun 5, 2018
@MikhailArkhipov
Copy link

No miracles here it is .NET startup. VSC waits until initialization completes.

@MikhailArkhipov MikhailArkhipov self-assigned this Aug 9, 2018
@MikhailArkhipov
Copy link

OK, I can reduce it ~30-40%. Does not affect actual completion availability time, but awaiting in the activator is quite a bit shorter so UI won't get blocked for as long.

@MikhailArkhipov
Copy link

microsoft/PTVS#4634

@MikhailArkhipov
Copy link

microsoft/PTVS#4645

@lock lock bot locked as resolved and limited conversation to collaborators Sep 12, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-intellisense LSP-related functionality: auto-complete, docstrings, navigation, refactoring, etc. debt Covers everything internal: CI, testing, refactoring of the codebase, etc.
Projects
None yet
Development

No branches or pull requests

3 participants