microsoft / microsoft/component-detection
Investigate performance of `PipComponentDetector`
Open
Nobody has claimed this yet.
detector:pip
status:requirements
type:refactor
- Dominant language
- C#
- Stars
- 553
- Forks
- 135
- Avg merge
- 20h 58m
- Merged PRs (30d)
- 6
Description
We're receiving some support emails about poor performance for large Python projects. We should profile this detector, identify any hotspots, and optimize them. Potentially related to #108
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
Locate PipComponentDetector and review related issue #108 first; profile it on large Python projects to identify hotspots. Done means the hotspots are optimized and performance is measured again.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, python
- Domain
- devtools, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100