You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 12, 2020. It is now read-only.
Current implementation of Codegen is using simple loop for code generation. Maybe it would be better to use Parallel.For or other multithread mechanism?
The text was updated successfully, but these errors were encountered:
Parallelism introduces a lot of issues we'd need to resolve. First we'd need to get some hard numbers. How long does it take for generators to run, in comparison with the whole run time of the Tool? Are these costs comparable?
If we can definitely prove that code generation takes most of the time, and not the warm-up and actual compilation before generators are invoked, we can proceed with implementation.
For exactly that purpose, I'll open a new issue to add performance tracking somehow into the Tool. Total run time of the Tool is registered by MSBuild anyway. So then we'll be able to compare these values.
Current implementation of Codegen is using simple loop for code generation. Maybe it would be better to use Parallel.For or other multithread mechanism?
The text was updated successfully, but these errors were encountered: