microsoft / microsoft/SizeBench
Parallelize analysis to help with large binaries
Open
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 175
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
When looking at large PDBs (like msedge.dll.pdb, chrome.dll.pdb) sizebench can take hours on my heavy duty dev box. Seems like there is an opportunity for performance improvement by utilizing more cores.
For example, the below has been running for 15 hours.
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 reproducing the analysis of a large PDB such as msedge.dll.pdb or chrome.dll.pdb, then trace the analysis pipeline to identify work that can run concurrently. Done means large-binary analysis uses more available cores and completes substantially faster than the reported 15-hour run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- devtools, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100