As an additional data point, my experience is that the interactivity of my machine is not noticeably impacted when I overcommit with -j12 on my 4core/8thread i7 windows machine. Task manager shows the cores often pegged at 100%, but the machine basically behaves normally. Neither is my Ubuntu 8core/16thread/-j16 (sometimes -j24) linux box noticeably affected when it's fully pegged.
Clearly it depends what you're trying to do, but for my uses, I just spin up a build and do other things normally until it's done, regardless of how over-committed it is. ----- Original Message ----- From: "Karl Tomlinson" <mozn...@karlt.net> To: dev-platform@lists.mozilla.org Sent: Tuesday, October 2, 2012 3:05:55 PM Subject: Re: mach has landed On Fri, 28 Sep 2012 11:44:56 -0700, Gary Kwong wrote: >> http://blog.johnford.org/new-mac-builders-ssds-j-settings/ > > Quoted from that blog: > > "I did find that it is better to set the -j setting too high than > it is to set it too low." > > -Gary Better in terms of build time, which is the right metric for a dedicated build machine. But bear in mind that a developer is usually trying to use the machine at the same time as doing a build. Adding more context switching load to the system without significantly improving build times is not necessarily a win for the developer. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
