Windows unusable when nrf Connect runs a build

With SDK 3.0.2 and 3.1.0 we noticed that during a build, even a 10-core i7 becomes almost unusable. The reason seems to be that all cc1.exe compiler processes run at normal priority instead of below normal.

Currently, we have to rely on a paid 3rd-party tool which automatically lowers the priority of every new cc1.exe process. Otherwise, Windows is completely unresponsive during the build.

With SDK 3.1.0 this issue becomes even more painful: due to some build system changes, full rebuilds happen much more frequently (for example:

  • Action: pristine build → ~4 minutes → done

  • Action: flash → again ~4 minutes of rebuilding).

This completely kills a fast development cycle.

Is there an official or recommended way in VS Code + nRF Connect to run west build / ninja at below normal priority so that all spawned processes (cc1.exe and others) inherit it?

Related