Date: Wed, 11 Feb 2009 00:07:33 +0100 From: Ivan Voras <ivoras@freebsd.org> To: "Bruce M. Simpson" <bms@freebsd.org> Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, Ken Smith <kensmith@cse.buffalo.edu>, src-committers@freebsd.org, Ken Smith <kensmith@freebsd.org> Subject: Re: svn commit: r188439 - head/release Message-ID: <9bbcef730902101507k4d1f4001r50f6b96504c7156@mail.gmail.com> In-Reply-To: <4991BA1C.4020209@FreeBSD.org> References: <200902101511.n1AFBQXx096922@svn.freebsd.org> <9bbcef730902100717x1cd1118bg1d2683a42a25232@mail.gmail.com> <1234279584.65150.13.camel@bauer.cse.buffalo.edu> <4991BA1C.4020209@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
2009/2/10 Bruce M. Simpson <bms@freebsd.org>: > I'd argue -j2 is appropriate, given that it is reasonable to assume most of > the user base still have uniprocessor systems. > > I have only one dual-core box, and -j2 will still cause at least one make(1) > child process to run at any given time on each core -- it seems like the > right compromise. I don't want to argue this into a bikeshed (I use -jX as appropriate to the NCPU of my systems so I'll tweak it appropriately whatever the consensus happens to be) but I haven't deployed a 32-bit *or* UP server *at all* in about a year and a half. In this time, only one of about 20 servers (yes, I don't have big installations :) ) was single dual-core, one was dual dual-core, and the rest quad and dual quad core. I don't consider myself to be a big admin, but I do consider these trends indicative of newly deployed servers at large. (also, I respect the embedded crowd, all this may not apply to them :) ).
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9bbcef730902101507k4d1f4001r50f6b96504c7156>