Date: Thu, 12 Apr 2007 21:07:57 +0200 From: Benjamin Lutz <mail@maxlor.com> To: freebsd-ports@freebsd.org Cc: Garrett Cooper <youshi10@u.washington.edu> Subject: Re: parallel builds revisited Message-ID: <200704122108.01376.mail@maxlor.com> In-Reply-To: <461DF6A3.9030201@u.washington.edu> References: <200704100452.40574.mail@maxlor.com> <1176363454.72184.2.camel@pav.hide.vol.cz> <461DF6A3.9030201@u.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
--nextPart1905326.VZ0lf1cZNu Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thursday 12 April 2007 11:06, Garrett Cooper wrote: > I dunno how you want to approach this, but gmake does recommend 2 > jobs be run in parallel for HTT enabled chips, and 3 or 4 jobs for a > dual core machines. > -Garrett So far the approach is one job per CPU. I'll do some benchmarks lateron=20 to determine wether it really helps to run more jobs. For the KDE=20 ports, my gut feeling is that the improvement would be negligible. I'll=20 have to evaluate non-C++ ports like gnome-*, where the compilation time=20 per file is shorter. Of course, to make proper use of distcc, at least #cores + 1 jobs are=20 required. I'll keep that in mind. Cheers Benjamin --nextPart1905326.VZ0lf1cZNu Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQBGHoORzZEjpyKHuQwRAiVCAJ9KyB2EDsNunMxXLvGhTdu3cx8jfgCeKf9D /xa+6/Q/BIJQxCOSodKVSXA= =B0mZ -----END PGP SIGNATURE----- --nextPart1905326.VZ0lf1cZNu--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200704122108.01376.mail>