Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Investigate performance of PipComponentDetector #373

Open
JamieMagee opened this issue Nov 23, 2022 · 2 comments
Open

Investigate performance of PipComponentDetector #373

JamieMagee opened this issue Nov 23, 2022 · 2 comments
Labels
detector:pip The pip detector status:requirements Full requirements are not yet known, so implementation should not be started type:refactor Refactoring or improving of existing code

Comments

@JamieMagee
Copy link
Member

JamieMagee commented Nov 23, 2022 •
edited
Loading

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
@RushabhBhansali
Copy link
Contributor

Related support request to investigate:
https://dev.azure.com/mseng/AzureDevOps/_workitems/edit/2010996

@cobya cobya added status:requirements Full requirements are not yet known, so implementation should not be started type:refactor Refactoring or improving of existing code detector:pip The pip detector labels Jan 5, 2023
@melotic melotic mentioned this issue Feb 16, 2023
Merged
@melotic melotic mentioned this issue Mar 6, 2023
Closed
@melotic
Copy link
Member

melotic commented Jun 26, 2023

Might be closed by #629

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
detector:pip The pip detector status:requirements Full requirements are not yet known, so implementation should not be started type:refactor Refactoring or improving of existing code
Projects
Component Detection - Detector Improvements
Status: Backlog
Milestone
No milestone
Development

No branches or pull requests
4 participants
@JamieMagee @cobya @RushabhBhansali @melotic