> Date: Fri, 12 Apr 2024 07:58:28 +0200 > From: Henrik Carlqvist <[email protected]> > Cc: [email protected], [email protected] > > On Fri, 12 Apr 2024 02:13:36 +0100 > Matt Staveley-Taylor <[email protected]> wrote: > > Browsing the mailing list I can see that the behaviour of -j with no > > arguments has been discussed a few times. Given it would affect > > backwards compatability to change how -j works, introducing a new > > flag seems appropriate. > > Yes, it has been discussed. I would not mind if the default without argument > for -j would be to limit to nproc or nproc+1, instead of like now, creating a > fork bomb when compiling a big project.
Isn't nproc or nproc+1 too much? On systems with hyper-threading, this will try using too many jobs, and might cause the system be significantly less responsive. Maybe nproc/2 is a better default?
