microsoft / microsoft/AttackSurfaceAnalyzer
GUI Based Analysis is Orders of Magnitude Slower Than CLI
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 3k
- Forks
- 294
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
With a large database (tested with 300+MB) analysis that takes only a few seconds directly with the CLI takes quite a while on the GUI, and there is no real progress notification.
Expected behavior
I think we should add a button to skip writing the analysis results to the database if possible, perhaps storing them in AppState, which is I suspect the bottleneck.
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
No files or tests are named. Start by locating the GUI and CLI analysis entry points, then compare their database-write behavior on a large database. Done should include a measured explanation of the slowdown and, if the proposed approach is viable, an optional way to avoid storing analysis results while providing meaningful progress notification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- cli, databases, desktop, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100