NG Builds takes 5 minutes on Build Server (build agent)

Bug Report or Feature Request (mark with an x)

My build agent is building the project ng build on a build server (windows) which has 32 cores. The problem is when building the project it only runs 1 core to 100% and all other cores are doing nothing. Is there a option or can we change that somehow in a setting? Now it takes 5 minutes and I think if it uses more cores it will be seconds…

Versions.

CLI 1.4.0-beta-0 NPM 5.3.0 Node 8.3.0

Repro steps.

ng build --prod

The log given by the failure.

Desired functionality.

Needs to be faster, is there a option to use all cores?

Mention any other details that might be useful.

Windows Server with 32 cores.

[egervari]

I also fully encourage the use of multiple cores. My CPU utilization is only 16-20% throughout the entire build process, and it takes 3 minutes for me. Memory is at 2gb. Disk usage is 0%.

I’m upgrading to an i7-8700k soon - and that’s going to have 6 cores. Yes, the cores will run at a higher clock speed, but my current CPU is already running at 4.2ghz so I’m not expecting as big of a jump as I would like.

It would be amazing if my 3 minute build time could go down to 30 seconds. Like omg I would give you a million hugs.

[JohannesRudolph]

I’d also highly appreciate if angular cli would try to actively use parallelization of build steps where this is achievable. We have a medium-sized project with over 200 components and around 20 modules. We have seen compile times increase a lot with every module that we add, so we’re currently at around 80s with AOT for a build on a Core i7-7700k (pretty much the fastest single thread desktop CPU you can get).

We’re building three variants of our app in parallel, so we can make up a bit for it but since each build needs ~2GB of RAM that’s not a nice load pattern for our CI servers, which therefore build sequential. We’d get a huge productivity boost from faster local builds running ng serve as well, which takes roughly 45s without AOT for initial display.

Have you seen this article here? https://medium.com/webpack/typescript-webpack-super-pursuit-mode-83cc568dea79 For sure it would speed up typescript compilation and then there’s still AOT, but I think it’s worth giving it a shot.

On a related note, the angular AOT compiler could theoretically build modules in parallel, couldn’t it? On first sight, that sounds like a plausible idea anyway.