Long idle time during production build process.

Bug report

What is the current behavior? Upgrading to latest Webpack v5 from v4 has increased production build times and culprit seems to be an idle process. Cold build time with v5 is around 70 - 80s and rebuilds are also 70 - 80s. Previously in v4, cold builds were around 45s and rebuilds were between 10-20s.

If the current behavior is a bug, please provide the steps to reproduce. Repo is available here: https://github.com/wasong/effective-guacamole I’ve stripped it to the bare minimum but left in the packages because I’m not sure what’s causing it. I’ve also included the cpuprofile data in the public folder for visibility. The 2 profile-real-* is from my app with all the files. The other 2 are generated from the issue repo.

You can see in the profiles that there is an idle process that doesn’t close for an extended period of time.

What is the expected behavior? Expected to build in similar time as v4.

Other relevant information: webpack version: 5.68.0 Node.js version: 16.14.0 Operating System: macos monterey 12.3 beta Additional tools:

[vankop]

@wasong mostly 2 passes minimize a bit more… this is not required option.

[wasong]

Okay, good to know. I’m not noticing any large size/performance differences so I’ll continue to use single pass for now. I think we can close this issue?