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

cpptools IntelliSense Updating and Parsing Wrokspace speed is much slower than previous versions #12292

Open
LittleFatHero opened this issue May 9, 2024 · 2 comments
Assignees
Labels
Language Service more info needed The issue report is not actionable in its current state performance

Comments

@LittleFatHero
Copy link

Environment

  • OS and Version: windows 10
  • VS Code Version: 1.89.0
  • C/C++ Extension Version: 1.20.5
  • If using SSH remote, specify OS of remote machine: ubuntu 20.04

Bug Summary and Steps to Reproduce

Bug Summary:
My vscode is running in windows 10 and I connected to remote machine ubuntu 20.04 which has installed vscode server and cpptools using the ssh remote-SSH extensions. when I open a C source file and go to definition of a function, it could not jump to the definition because cpptools is Updating IntelliSense and Parsing Workspace. So I wait for cpptools to finish the job, but I found that it Parsing Workspace is extremely slower than previous version. My workSpace has about 100000 C source files.

  1. Why cpptools 1.20.5 verison feels slow than previous version?
  2. what is strategy of when Updating IntelliSense and Parsing Workspace? will it updating of the file on the workspace or only update the and parse the open file?
  3. Would it be possible to add a setting that allows the user to specify number of thread to use for parsing?

Steps to reproduce:

  1. Open the workspce which has about 100000 C source Files using vscode 1.89.0 and cpptools 1.20.5
  2. Count the time it takes to finish update Intellisense and Parsing workspace.
  3. compare the time with privous version of vscode and cpptools

Expected behavior:
update Intellisense and Parsing workspace faster

Configuration and Logs

default config

Other Extensions

No response

Additional context

No response

@Colengms
Copy link
Collaborator

Hi @LittleFatHero . Would you be able to try out the various versions (including prerelease versions) between 1.89 and 1.20.5, to isolate which version seems to introduce the performance regression?

@browntarik browntarik added performance Language Service more info needed The issue report is not actionable in its current state labels May 13, 2024
@LittleFatHero
Copy link
Author

Hi @LittleFatHero . Would you be able to try out the various versions (including prerelease versions) between 1.89 and 1.20.5, to isolate which version seems to introduce the performance regression?

ok, I will try it as soon as possible

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Language Service more info needed The issue report is not actionable in its current state performance
Projects
None yet
Development

No branches or pull requests

3 participants