microsoft / microsoft/ApplicationInspector
Test performance uplift with StreamRegex
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 4.4k
- Forks
- 366
- Avg merge
- 6d 7h
- Merged PRs (30d)
- 3
Description
Is your feature request related to a problem? Please describe.
A large portion of the execution time for AppInspector is allocating memory for the FullContent field of TextContainer. We should test the performance uplift we can get by using StreamRegex.
Difficult portions here will be properly implementing the conditions based behavior from OAT and optimizing number of passes through the stream with multiple rules.
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 TextContainer.FullContent, OAT condition behavior, and StreamRegex but no files or tests. Start by locating those references and establish a performance comparison for the current implementation versus StreamRegex; done means measured uplift and validated condition handling with efficient stream passes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- performance, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100