Ayup ... anything over -j2 is probably more trouble than it's worth, even on a multi-processor or cluster. You want your CPU utilization *at* 100 percent; you can't get it *over* 100 percent.
I beg to differ. The point is to do as many tasks as possible *at the same time*, as opposed to waiting for a couple to finish before going to the next. I build stuff on a 16 processor box quite often, and let me assure you that applications which actually parallelize their build processes go *much* faster passing 20 make jobs rather than just 2 or 3.
In fact, nothing pisses me off more when an ebuild forces -j1 on me. I've been pondering filing upstream bugs on every single program that has issues building parallel like this.
Steve
-- [email protected] mailing list
