IssueRaiser

Support multi-threaded compilation for --build

## Search Terms Project references, multi-thread, compilation, performance ## Suggestion We have migrated our main project to use project references. It simplifies the development workflow, but brings basically 0 noticeable performance improvement (for both local development and CI). There's even an illusion that now we get worse performance during development. I guess the main reason behind this is lacking support for multi-thread compilation. ## Use Cases Improve compilation performance. ## Examples N/A ## Checklist My suggestion meets these guidelines: * [x] This wouldn't be a breaking change in existing TypeScript/JavaScript code * [x] This wouldn't change the runtime behavior of existing JavaScript code * [x] This could be implemented without emitting different JS based on the types of the expressions * [x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.) * [x] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).

Posted by vilicvane on Mar 6, 2019, 6:41 AM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.4,000 issues0 comments

support (Software)

Support multi-threaded compilation for --build

vilicvaneMar 6, 2019, 6:41 AM

## Search Terms Project references, multi-thread, compilation, performance ## Suggestion We have migrated our main project to use project references. It simplifies the development workflow, but brings basically 0 noticeable performance improvement (for both local development and CI). There's even an illusion that now we get worse performance during development. I guess the main reason behind this is lacking support for multi-thread compilation. ## Use Cases Improve compilation performance. ## Examples N/A ## Checklist My suggestion meets these guidelines: * [x] This wouldn't be a breaking change in existing TypeScript/JavaScript code * [x] This wouldn't change the runtime behavior of existing JavaScript code * [x] This could be implemented without emitting different JS based on the types of the expressions * [x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.) * [x] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).

Comments (0)

No comments yet. Start the discussion.

Comment on this issue