Parallelize analysis to help with large binaries

Open
#39 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
csharp
Domain
devtools, performance

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.

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.

image

Dominant language
C#
Stars
175
Forks
20
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/SizeBench

All issues in microsoft/SizeBench

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.