microsoft / microsoft/vscode-cpptools
Find All References is really slow for this project
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
See the repro details at https://github.com/microsoft/vscode-cpptools/issues/5376 . That issue got fixed, but the performance is unusually slow. I wasn't able to get Find All References to work in VS for comparison. There may be some performance bug. There might be a recursive includes and tag parser cause for the slowness in addition to IntelliSense parsing. The unification work may or may not improve this, but it would be a good test case to see if performance got better or worse after the unification work changes.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the reproduction details in microsoft/vscode-cpptools#5376 and measure Find All References on this project. Investigate whether recursive includes, the tag parser, or IntelliSense parsing account for the slowness, and compare performance before and after the unification work; done means a confirmed cause or a measurable performance result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- performance, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100