On Friday, December 6, 2002, at 04:51 PM, Chris Leishman wrote:
AFAIK, there is absolutely no point in using -j2 except on systems that have more than one processor, which is not that many in the MacOS X world. Almost all make tasks should be cpu or disk io intensive, so having more tasks running than the system can service at one will simply result in additional memory use and contention (especially if memory is low) and additional context switches. This will simply _slow the builds down_.According to Jim Magee (i believe) on the apple list, in his experience -j2 (I think he actually suggested -j3) helps even on single processor systems.
Every power mac sold (for the past 6 months) is dual processor. Its an all-dual lineup.
I would highly doubt many users systems would be dual processor (let alone 4-way, which would be needed for -j4), so I really wonder why developers are using these
Yeah, it is annoying when that happens. I was annoyed too when my system slowed down. I think Ben removed the high -j numbers already from the new kde packages.
Sorry for being so blunt about this, but I've just had my powerbook grind to a halt a couple of times and I finally figured out that this was the problem (I was building qt3, and one c++ compile process takes up enough memory as it is - with 4 I was down to only 17% actual cpu usage and about 10000 page in/outs per second, which is useless).
-Ben
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel
