PowerShell / PowerShell/PSResourceGet
Find-Module -Command need perf improvement
Open
Nobody has claimed this yet.
Area-Find
- Dominant language
- C#
- Stars
- 576
- Forks
- 114
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 7
Description
As part of https://github.com/PowerShell/PowerShell/issues/1982, if the user types a command that doesn't exist, we want to be able to search PSGallery and inform the user to install a module. However, the current execution of Find-Module -Command foo takes ~4.5s, this needs to be closer to 100ms (or less).
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 by running Find-Module -Command foo and tracing the PSResourceGet execution path that searches PSGallery. Compare the current roughly 4.5-second runtime with the requested target; done means the search completes in about 100 ms or less while still supporting the intended command lookup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, powershell
- Domain
- cli, performance
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100