EDIT: Tried nice -n +19, still lags my other programs.
yea, this is wrong way of doing things. You should have better results with CPU-pinning. Increasing priority for YOUR threads that interact all the time with disk io, memory caches and display IO is the wrong end of the stick. You still need to display compilation progress, warnings, access IO.
There’s no way of knowing why your system is so slow without profiling it first. Taking any advice from here or elsewhere without telling us first what your machine does is missing the point. You need to find out what the problem is and report it at the source.
The CPU is already 100% busy, so changing number of compilation jobs won’t help, CPU can’t go faster than 100%.
Yeah this survey is super inappropriate and offensive. Please do not ask such personal questions.
Did you notice that more inappropriate questions appear and disappear based on your previous answers?
Linux 6.6 (which recently landed on Debian) changed the scheduled to EEVDF, which is pretty widely criticized for poor tuning. 100% busy which means the scheduler is doing good job. If the CPU was idle and compilation was slow, than we would look into task scheduling and scheduling of blocking operations.