Date: Mon, 10 Feb 2014 08:03:47 -0700 (MST) From: Warren Block <wblock@wonkity.com> To: Tim Daneliuk <tundra@tundraware.com> Cc: freebsd-stable@freebsd.org Subject: Re: And Here I Thought buildworld/makeworld Was IO Bound Message-ID: <alpine.BSF.2.00.1402100757200.13608@wonkity.com> In-Reply-To: <52F84AF8.8050007@tundraware.com> References: <52F84AF8.8050007@tundraware.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 9 Feb 2014, Tim Daneliuk wrote: > For some years now, I have been doing nightly builds of -STABLE > on an old Pentium D machine with 2G of memory. Buildworld + 2 > different kernels was taking in the neighborhood of 3 1/2 hours or so > to run. > > I then upgraded the Mobo/CPU to a Haswell Quadcore I5-4570 and, sure > enough, the build time for all the above came down to 30-35 mins or so. > > "So", says I, "I'll bet a faster drive would help considering all the > scribbling to the disk the compilers and makes do". So, I upgdared to > a Kingston SSD Now 300, 120G hard drive and he time to do the above > went down to .... wait, it's still about 30-35 mins ???? > > So, I've tried fiddling with different values for -j on the make > command line to little avail. Well, -j8 and -j16 show no real > difference here. > > So is the bounding function here actually CPU not IO? Am I missing > something? Yes, it mostly is CPU. Make sure you are running powerd on that i5, it enables turbo mode and gives a noticeable speed increase. Also, consider using -DNO_CLEAN, leaving all the untouched object files in place for make to find and skip. I've seen buildworld times under a minute with that on my i5 and SSD. There are downsides (uname is not always updated correctly), but removing /usr/obj every so often and starting from scratch will fix that.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1402100757200.13608>