PowerShell / PowerShell/PowerShellEditorServices
[Performance] Improve/address file searching especially for large workspaces
Open
Nobody has claimed this yet.
Area-Engine
Issue-Performance
- Dominant language
- C#
- Stars
- 767
- Forks
- 266
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 1
Description
There are significant performance impacts on projects with a large number of files in a workspace because of the way and frequency PSES searches through all of the files in a workspace
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
The issue names no files, tests, or entry points. Start by locating PSES's workspace-wide file-search implementation and measuring its frequency on a large workspace. Done means file searching no longer causes significant performance impacts in large workspaces, with evidence from an appropriate performance check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- devtools, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100