Date: Sun, 04 Nov 2007 12:40:46 +0100 From: Kris Kennaway <kris@FreeBSD.org> To: Christian Baer <christian.baer@uni-dortmund.de> Cc: freebsd-sparc64@freebsd.org Subject: Re: Doesn't anything work around here? Message-ID: <472DAFBE.9070603@FreeBSD.org> In-Reply-To: <fgka0g$185e$4@nermal.rz1.convenimus.net> References: <ffg2gk$1n1r$1@nermal.rz1.convenimus.net> <200711011822.25884.linimon@lonesome.com> <472B39A8.3070708@alaska.net> <fgka0g$185e$4@nermal.rz1.convenimus.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Christian Baer wrote: > On Fri, 02 Nov 2007 06:52:24 -0800 Royce Williams wrote: > >> I've started a couple of threads in the past about offering to chip in >> for hardware to support builds, and especially sparc64 freebsd-update. >> To move forward on that, what is the 'best bang for the buck' hardware >> that the project could use? > > The fastest CPU that are currently supported by FreeBSD are 650MHz IIi. > You can find that in a Blade 150. There are no workstations with more than > one CPU of this type around (that I know of). > > The U80 has up to four 450MHz CPUs. So this is (probably) the fastest > sparc64-workstation currently supported by FreeBSD. Since the ports cannot > be compiled with more than one job at a time (make -j 2 breaks most of the > builds), I'm not sure if more than one CPU would be of much use - for > building the ports. However, if only one job is run, the workstation would > still be usable for other things while compiling. That is no problem, even on single CPU machines I run concurrent builds since it turns out to be more efficient. In the past we have even used 14 CPU e4500 machines for package builds although they all died from hardware failure. Kris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?472DAFBE.9070603>