-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
"Go To Symbol in Workspace..." searchs are not "snappy" on large projects #7914
Labels
enhancement
Improvement to an existing feature
fixed
Check the Milestone for the release in which the fix is or will be available.
Language Service
performance
Milestone
Comments
A significant update to Go To Symbol has been published in the insiders build - see #11557 |
bobbrow
added
the
fixed
Check the Milestone for the release in which the fix is or will be available.
label
Feb 13, 2024
This should be addressed in 1.19.4. |
This was referenced Mar 13, 2024
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
enhancement
Improvement to an existing feature
fixed
Check the Milestone for the release in which the fix is or will be available.
Language Service
performance
Bug type: Language Service
OS and Version: Windows10 (Version 2004)
VS Code Version: 1.58.2
C/C++ Extension Version: v1.5.1
"Go To Symbol in Workspace..."(CTRL+T) is very slow on large projects.
As a benchmark, I opened a workspace on Linux code base, and searched for "memory".
Results for the first search are abnormally long (~25 seconds). to be handled in another bug report (#7980)
Results for additinal searchs are around ~3s.
Since browsing large code bases requires many such searches, non-instant results becomes a burden.
Notes:
I set C_Cpp.intelliSenseEngine to "Tag Parser" (my preferred choice)
The workspace was fully parsed before running the search.
For comparison, on ** Source Insight IDE , results for the same symbol search are instant (<1s).**
Expected behavior
Full Workspace Symbols Search should return results faster (<1s)
The text was updated successfully, but these errors were encountered: