From owner-freebsd-hackers Fri Nov 12 11:12:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id B425A14C10 for ; Fri, 12 Nov 1999 11:12:15 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id MAA05287; Fri, 12 Nov 1999 12:12:13 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA18289; Fri, 12 Nov 1999 12:12:35 -0700 (MST) Message-Id: <199911121912.MAA18289@harmony.village.org> To: Ben Rosengart Subject: Re: make -jN world; how to determine optimal value of N? Cc: Assar Westerlund , hackers@FreeBSD.ORG In-reply-to: Your message of "Thu, 11 Nov 1999 17:59:29 EST." References: Date: Fri, 12 Nov 1999 12:12:35 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Ben Rosengart writes: : D'oh -- I *meant* to add "besides trying different values and measuring" : -- if I had that much time on my hands, I wouldn't be worrying about how : long a make world takes. :-) Generally on FreeBSD machines that are otherwise unused and flush with memory, the formula I've seen for n is 4 * #CPU. This appears to be the sweet spot in the curves for people that have run experiments. Beyond this point addtional jobs had no benefit or actually slowed things down, at least according to the few tests that were run. Of course there is the whole area file system tuning that also is important (having enough spindles, using soft update, noatime, etc). From experiments I did in the 3.0 time frame, I found that file system options could gain a PPro 200 about 10% for slow disks and as much as 25% for very fast disks. The cc options also had a minor effect (on the order of 5% iirc). I took an untuned make buildworld down from about 1:50:00 to 1:05:00 by using the above tuning (and building on newer, faster disks). My machine wasn't flush enough with memory (only 96mb at the time) for me to contemplate adding -j to the mix. Others have reported improvements in the few percent range. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message