Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Consider parallelizing the crossgen phase of the installer build
See original GitHub issueIt currently looks like the crossgen phase of the installer build is done in serial rather than parallel. It would likely be worthwhile to change this up to be parallelized instead to take full advantage of the underlying hardware.
This is currently done via MSBuild batching: https://github.com/dotnet/arcade/blob/cc0bbc15d0b038b4949bc0c45f3436973ec11106/src/Microsoft.DotNet.Build.Tasks.SharedFramework.Sdk/targets/framework.dependency.targets#L408
This would likely need to be changed to be a parallel <MSBuild Projects="$(MSBuildThisProjectFullPath)" ... but may require various props/etc to be transferred over.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:4
- Comments:8 (8 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
We should also add
-nologoto the calls so we don’t end up with interleaved output, and to reduce log spam.Edit: This bit already done by https://github.com/dotnet/arcade/pull/4567. 🙂
Well, we’re going whatever the SDK does now, so not really? I don’t think they paralelize so we might have some work to do for this, but we’d want to do it in the SDK.